Networking Issue with CentOS containers in 1.6

[lp86]

I have had problems since the 1.6 update and also on clean 1.6 installs to create a CentOS 4/5 container. When I start it up, the networking does not work. I discovered that if I restore the contents of the pre 1.6 version of /etc/sysconfig/network-scripts/route-venet0 everything starts working again. I have to make it immutable or it will get deleted by the script which sets up the networking.

I just installed 1.6 and downloaded the CentOS 5.2 standard template from Proxmox. It does the same thing, no networking until that file is restored.

 

[dredd0606]

We are having the same issue. Not having used Proxmox before, we have nothing to restore from, so all Cent based appliances are toast for us...

Any ideas?

- Dredd

 

[dietmar]

I just installed 1.6 and downloaded the CentOS 5.2 standard template from Proxmox. It does the same thing, no networking until that file is restored.

I just tested with 'centos-5-standard_5.2-1_i386.tar.gz' and network works without problems.

What is the output of

# pveversion -v

 

[lp86]

pve-manager: 1.6-5 (pve-manager/1.6/5261)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-24
pve-kernel-2.6.32-4-pve: 2.6.32-24
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-22
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

 

[lp86]

I just tested it again (CentOS 4), when I remove the immutable bit from "/etc/sysconfig/network-scripts/route-venet0" and restart the container, the networking does not work.

 

[tom]

works on my test system out of the box (with venet).

 

[dietmar]

I just tested it again (CentOS 4), when I remove the immutable bit from "/etc/sysconfig/network-scripts/route-venet0" and restart the container, the networking does not work.

Please can we clarify the issue using CentOS 5

 

[tom]

just tested here: clean install of proxmox ve, downloaded our centos 4 templates (also centos 5 is working), using venet.

so how can we reproduce your issue here?

my system:

pveversion -v
pve-manager: 1.6-7 (pve-manager/1.6/5277)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-25
pve-kernel-2.6.32-4-pve: 2.6.32-25
qemu-server: 1.1-23
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-2
ksm-control-daemon: 1.0-4

 

[lp86]

The initial problem with the plain CentOS systems appears to have been fixed with one of the updates that came out after the initial release of 1.6.

However I am still having issues with BlueQuartz (CentOS 4) and BlueOnyx (CentOS 5).

On these systems this file "/etc/sysconfig/network-scripts/route-venet0" has to exist in its pre 1.6 state or the container does not have any network access.

I was using vzdump/vzrestore to move a virtual machine to another node. I noticed that my chattr'ed files lost their protection when they were restored. Is this a bug or intended feature?

 

[dietmar]

On these systems this file "/etc/sysconfig/network-scripts/route-venet0" has to exist in its pre 1.6 state or the container does not have any network access.

The maintainers of those templates should fix that.