OpenVZ network problem

D

dcrobinson

New Member
Dec 5, 2010
18
0
1
Malvern, UK
www.36arn.co.uk
I have a number of openvz VMs, using the Debian 6 PVE template. These use a mix of venet and vmbr networking. They are all working fine.

For some inexplicable reason, if I now try to deploy a new VM, everything seems to work, except that the new machine cannot ping the network gateway. It can ping other machines in the LAN, and the VM host, but the gateway is unreachable.

I have also tried deploying a Debian 5 template. That gives me a SIOCADDRT when I try to use the network.

Any suggestions? The weird thing is that everything else is still working.
 
Some more information.

If I do a "route -n", I get the same output from both the working and non-working containers:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 venet0

Also, the /etc/network/interfaces files are identical on both (except for the "address" line, obviously).
 
post the output of 'pveversion -v'
 
pveversion -v output:

pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.18: 1.8-14
pve-kernel-2.6.32-4-pve: 2.6.32-32
pve-kernel-2.6.18-5-pve: 2.6.18-14
pve-kernel-2.6.18-4-pve: 2.6.18-10
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.26-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-14
 
you installed the virtual package for 2.6.18 (proxmox-ve-2.6.18) but you booted the 2.6.32 kernel.

edit /boot/grub/menu.lst that the 2.6.18 is default and reboot. and think of removing the 2.6.32 kernel.
 
OK, thanks, I'll try that.

Any reason why I shouldn't stick with 2.6.32, (and install the proxmox-ve-2.6.32 package) or is 2.6.18 better for OpenVZ? I have a mix of OpenVZ and KVM virtual machines, although to be honest I am most concerned about the performance/stability of the KVM ones.
 
2.6.18 is still the only stable OpenVZ branch. 2.6.32 misses some feature like openvz live-migration is not reliable, cpu limits. if you do not need this feature OpenVZ on 2.6.32 is quite ok as its the next upcoming stable branch.

and yes, KVM performance is 'generally' better on 2.6.32, but also 2.6.18 is not bad, a lot of backports.
 
Thanks for that advice. I have now sorted out the boot inconsistency, and have opted for 2.6.32.

I now feel a complete fool - I finally worked out the problem. My gateway router had an old IP address binding to an ancient physical machine (long since dead). So it was rejecting any packets from my new VM.

Thanks for your help, and I will make a donation to the project.
 
thanks for feedback and the donation!
 
You must log in or register to reply here.
Top Bottom