OpenVZ container networking trouble

RRJ

Member
Apr 14, 2010
245
0
16
Estonia, Tallinn
Hello,
First of all - proxmox is a very nice v. system, thank you
now about the problem:
i've installed proxmox without any problems, downloaded the karmic 9.10 ubuntu container from openvz site, installed it and run. but when i restart the container, after restart there is no network
ifconfig says nothing.
i have to bring every interface in the container manually:
ifconfig lo up
ifconfig venet0 up
ifconfig venet0:0 up

here is config from container:
root@cacti:~# cat /etc/network/interfaces
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
# Please create/edit /etc/network/interfaces.head and /etc/network/interfaces.tail instead,
# their contents will be inserted at the beginning and at the end
# of this file, respectively.


auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
broadcast 127.255.255.255
up ip route replace 127.0.0.0/8 dev lo


# Auto generated venet0 interface
auto venet0
iface venet0 inet static
address 127.0.0.1
netmask 255.255.255.255
broadcast 0.0.0.0
up route add -net 192.0.2.1 netmask 255.255.255.255 dev venet0
up route add default gw 192.0.2.1
auto venet0:0
iface venet0:0 inet static
address 192.168.250.219
netmask 255.255.255.255
broadcast 0.0.0.0

and host

sisemon:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
address 192.168.250.220
netmask 255.255.255.0
gateway 192.168.250.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
 
proxmox doesnt have 9.10 images.

so any1 to help me? got in trouble. trying to use proxmox on production, but such problem could make me switch to something else.. :(
 
To all of those, who will face same problem:
just remove the networking from startup
#update-rc.d -f networking remove
and then get it back again
# update-rc.d networking defaults
did the trick for me, now network starts on container start.
 
While it does work, I am not sure that RRJ's fix is a correct way to handle this problem...

Been playing around with this on test VMs - it seems that the problem starts happening after "apt-get upgrade" installs ifupdown 0.6.8ubuntu21.2 (which is an update from 0.6.8ubuntu21) - the changelog for it doesn't really give a clear further clue on what might have changed to break this ;/