Blog posts

Blog full archive

Windows Server 2003 shutdown Group Policy

Because I always forget about this one…

http://pve.proxmox.com/wiki/Acpi_kvm

For Server 2003 (and 2008) run

gpedit.msc

and change the key

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Shutdown: Allow system to be shut down without having to log on

Yumex setup on Fedora 17 LDXE

Yumex (I’ll probably remove it later, but it might be handy for removing cruft) complains that it can’t download stuff and bombs out. Even if yum proxy has been set and yum is working.

To fix, edit /etc/yumex.conf and add the proxy in:

proxy = "http://your.cache.address:port"

The quotes are required!

Some information about the grub font error at http://unsolicitedbutoffered.blogspot.co.uk/2012/06/fedora-17-lxde-review-just-facts-mam.html

Migration of virtual machines from Proxmox 1.9 to 2.1

Procedure

  1. Create a storage area that both clusters can see (e.g. NFS on freenas box)
  2. Backup VM from 1.9 system to backup area.
  3. SSH to backup area and move backup tgz file from root of share (where 1.9 backs up) to dump directory (should have been created by connecting 2.1).
  4. Restore from backup in 2.1 (may want to keep the same VMID, to avoid inconsistent disk image numbers)
  5. Change hardware if required (VM won’t start if pointing to non-existent CD image, change network to appropriate bridge)

Network interface in Windows VMs

Not sure at moment whether changing the bridge affects anything, or whether it’s just due to the migration, but windows sees the network interface as a new device, so sets it using DHCP. Check via console!

Dokuwiki odd behaviour with <code> and <code text> syntax parser

Compare <code> and <code text> blocks:

<code>
*filter

# This will allow all loopback (lo0) traffic and drop all traffic to 127/8
# that does not use lo0
-A INPUT -i lo -j ACCEPT
-A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT

#  This accepts all already established connections
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

# This allows all outbound traffic
-A OUTPUT -j ACCEPT
</code>

<code text>
*filter

# This will allow all loopback (lo0) traffic and drop all traffic to 127/8
# that does not use lo0
-A INPUT -i lo -j ACCEPT
-A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT

#  This accepts all already established connections
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

# This allows all outbound traffic
-A OUTPUT -j ACCEPT
</code>

In dokuwiki text formatting option adds single spaces in the blank lines. Not helpful in the case of iptables rules files, where these spaces break the parser…

More Proxmox 2.1 setup notes - corosync

Way to change primary interface – edit /etc/hosts to change ip address returned when cman does lookup of system hostname.

e.g.

127.0.0.1 localhost.localdomain localhost
192.168.40.6 Hildasay.physics.gla.ac.uk Hildasay pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

With this config cman will return 192.168.40.6 as the address totem should bind to for its multicast stuff.

There may be certificate problems doing this. Probably best in future to install Proxmox with the initial interface on the SAN (or other appropriate private network).