Since upgrading to vserver-sources-2.3.0.36.14-r1 (from 2.3.0.35.6), the hostname seems to be global for all VMs and the host machine. This means that setting/changing the hostname in any VM will affect all other VMs as well as the host machine. This makes the whole setup mostly unusable. Going back to the older kernel fixes the problem again, so it's definitely kernel-related. Reproducible: Always Steps to Reproduce: 1. Start a VM with vserver-sources-2.3.0.36.14 2. Inside the VM, run 'hostname abcd.example.net' 3. Exit the VM, check 'hostname' on the host machine Actual Results: The host machine will now display 'abcd.example.net'. Expected Results: Changing the hostname in any VM shouldn't affect others, much less the host machine.
you need util-vserver-0.30.216_pre* for proper namespace support in newer kernels
