No internet within OpenVZ containers

[macamba]

I use vnet for OpenVZ containers but it seems that during updating to later Proxmox host versions (currenlty on latest 3.1-24 ) the containers have no internet connectivity anymore.
KVM machines on the same host still have internet connectivity with no problems. Suggestions?

 

[tom]

I use vnet for OpenVZ containers but it seems that during updating to later Proxmox host versions (currenlty on latest 3.1-24 ) the containers have no internet connectivity anymore.
KVM machines on the same host still have internet connectivity with no problems. Suggestions?

what is "latest 3.1-24"? please post the output of 'pveversion -v' and/or compare with:

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.3

 

[macamba]

what is "latest 3.1-24"? please post the output of 'pveversion -v' and/or compare with:

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.3

See output below. I notice that I not upgraded to 3.3 yet. I issued apt-get update && upgrade, instead of apt-get update && dist-upgrade. Running apt-get dist-upgrade right now.

proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-15
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

 

[starnetwork]

OpenVZ WAN ip is from same class as the Proxmox IP?
if no, you need:

Edit: /etc/vz/vz.conf
Change from:
NEIGHBOUR_DEVS=detect
To:
NEIGHBOUR_DEVS=all
Restart OpenVZ:
/etc/init.d/vz restart

 

[macamba]

Yes, they are both from the same network class. Solving this issue I ran into another problem. After issuing apt-get update && dist-upgrade Proxmox it hang forever on the following line:
- update-initramfs: Generating /boot/initrd.img-2.6.32-34-pve

I had to interrupt the process and issue dpkg --configure -a, but again it hangs at the following line:
- update-initramfs: Generating /boot/initrd.img-2.6.32-34-pve

Suggestions?