upgrade to 1.5 and no network on debian Appliances

marco · Jan 20, 2010

Hi,

I 've updated today my system to 1.5 with apt-get update and so on..

Everythings works fine except a small glitches with my debian appliances, after the proxmox boot (to run the latest kernel version) they lost the network configuration of eth0 (which I previously added manually)

In the /etc/network/interfaces is stated that any modification shall go to file /etc/network/interfaces.head or /etc/network/interfaces.tail

It would be nice to know it before doing the upgrade to 1.5
(or it is related to the debian appliances?)

Marco

dietmar · Jan 21, 2010

marco said:
It would be nice to know it before doing the upgrade to 1.5

Sorry, but directly modifying that file never worked (OpenVZ writes that file).

svenr · Jan 21, 2010

This worked when using brigded interfaces till 1.4

dietmar · Jan 21, 2010

svenr said:
This worked when using brigded interfaces till 1.4

Yes, it should works when you use bridged interfaces. Please can you send me the VM config (/etc/vz/conf/<vmid>.conf), directly to dietmar@proxmox.com?

marco · Jan 21, 2010

maybe I confuse you, but the migration from proxmox 1.3 to 1.4 the debian appliance gave me any error in the debian appliance.
The eth0 device in the appliance is a bridge device:

this is the config of my debian appliance:

Code:

# PVE default config for 256MB RAM

ONBOOT="yes"

# Primary parameters
NUMPROC="1024:1024"
NUMTCPSOCK="9223372036854775807:9223372036854775807"
NUMOTHERSOCK="9223372036854775807:9223372036854775807"
VMGUARPAGES="262144:9223372036854775807"

# Secondary parameters
KMEMSIZE="9223372036854775807:9223372036854775807"
OOMGUARPAGES="262144:9223372036854775807"
PRIVVMPAGES="262144:274644"
TCPSNDBUF="9223372036854775807:9223372036854775807"
TCPRCVBUF="9223372036854775807:9223372036854775807"
OTHERSOCKBUF="9223372036854775807:9223372036854775807"
DGRAMRCVBUF="9223372036854775807:9223372036854775807"

# Auxiliary parameters
NUMFILE="9223372036854775807:9223372036854775807"
NUMFLOCK="9223372036854775807:9223372036854775807"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="9223372036854775807:9223372036854775807"
LOCKEDPAGES="131072:131072"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="9223372036854775807:9223372036854775807"
PHYSPAGES="0:9223372036854775807"

# Disk quota parameters
DISKSPACE="157286400:173015040"
DISKINODES="30000000:33000000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-5.0-standard_5.0-1_i386"
ORIGIN_SAMPLE="pve.auto"
HOSTNAME="quantum.boscacci.ch"
DESCRIPTION="Debian 5.0 (standard)<br>10.20.0.1"
NAMESERVER="127.0.0.1 192.168.1.1"
SEARCHDOMAIN="example.com"
NETIF="ifname=eth0,bridge=vmbr3,mac=00:18:51:34:A2:7B,host_ifname=veth1100.0,host_mac=00:18:51:7A:2D:5C"

tom · Jan 21, 2010

marco said:

maybe I confuse you, but the migration from proxmox 1.3 to 1.4 the debian appliance gave me any error in the debian appliance.
The eth0 device in the appliance is a bridge device:

this is the config of my debian appliance:

Code:

# PVE default config for 256MB RAM

ONBOOT="yes"

# Primary parameters
NUMPROC="1024:1024"
NUMTCPSOCK="9223372036854775807:9223372036854775807"
NUMOTHERSOCK="9223372036854775807:9223372036854775807"
VMGUARPAGES="262144:9223372036854775807"

# Secondary parameters
KMEMSIZE="9223372036854775807:9223372036854775807"
OOMGUARPAGES="262144:9223372036854775807"
PRIVVMPAGES="262144:274644"
TCPSNDBUF="9223372036854775807:9223372036854775807"
TCPRCVBUF="9223372036854775807:9223372036854775807"
OTHERSOCKBUF="9223372036854775807:9223372036854775807"
DGRAMRCVBUF="9223372036854775807:9223372036854775807"

# Auxiliary parameters
NUMFILE="9223372036854775807:9223372036854775807"
NUMFLOCK="9223372036854775807:9223372036854775807"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="9223372036854775807:9223372036854775807"
LOCKEDPAGES="131072:131072"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="9223372036854775807:9223372036854775807"
PHYSPAGES="0:9223372036854775807"

# Disk quota parameters
DISKSPACE="157286400:173015040"
DISKINODES="30000000:33000000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-5.0-standard_5.0-1_i386"
ORIGIN_SAMPLE="pve.auto"
HOSTNAME="quantum.boscacci.ch"
DESCRIPTION="Debian 5.0 (standard)<br>10.20.0.1"
NAMESERVER="127.0.0.1 192.168.1.1"
SEARCHDOMAIN="example.com"
NETIF="ifname=eth0,bridge=vmbr3,mac=00:18:51:34:A2:7B,host_ifname=veth1100.0,host_mac=00:18:51:7A:2D:5C"

you migrate a container from 1.3 to 1.4? no supported and not tested.

anyways, go for the latest 1.5 and check again.

bleau69 · Jan 22, 2010

I have the same networking issue. This was a clean 1.4 ISO install and the VM was setup and installed in the clean 1.4 environment. Upgraded to 1.5 and the Ubuntu 8.04 /etc/network/interfaces never gets populated on reboot.

pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve5
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1

..conf snippet -

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="ubuntu-8.0-standard_8.04-1_i386"
ORIGIN_SAMPLE="pve.auto"
HOSTNAME="server.somename.com"
NAMESERVER="127.0.0.1"
SEARCHDOMAIN="myhostname.net"
NETIF="ifname=eth0,mac=D2:3D:4C:3D:22:11,host_ifname=veth56289.0,host_mac=00:18:51:A5:55:6C"
IPTABLES="ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp"
CAPABILITY="CHOWN

n DAC_READ_SEARCH

n SETGID

n SETUID

n NET_BIND_SERVICE

n NET_ADMIN

n SYS_CHROOT

n SYS_NICE

n "

I even downloaded the ubuntu-8.04-standard_8.04-3 and interfaces never gets populated and if I make manual changes, they don't persist through a reboot either.

MeneM · Jan 22, 2010

I can confirm this issue.

I have a ubuntu openvz that has a bridged interface. and on every reboot it looses it's /etc/network/interfaces content.

It does help if I put the content in /etc/network/interfaces.tail. But it took some searching before we saw this ;-)

dietmar · Jan 22, 2010

Please can you update - i already fixed that bug. There is also a new CD image on the server without that bug.

bleau69 · Jan 22, 2010

dietmar said:
Please can you update - i already fixed that bug. There is also a new CD image on the server without that bug.

Hi Dietmar,

I will burn the CD this afternoon and confirm success or failure.

MeneM · Jan 22, 2010

Without much testing: I can confirm it works now.

Petrus4 · Jan 23, 2010

I have the same issue after upgrading from 1.4 to 1.5: with a Ubuntu openVZ container lost its NIC.

I changed to bridged mode by clearing the venet ip address and set eth0 to vmbr0 then clicked on save.. after a refreshing the gui, eth0 goes back to disabled.

I recreated /etc/network/interfaces in the guest:

Code:

auto lo
iface lo inet loopback
 
auto eth0
iface eth0 inet static
        address 192.168.10.2
        netmask 255.255.255.0
        network 192.168.10.0
        broadcast 192.168.10.255
        gateway 192.168.10.1

and restarting networking

I cannot seem to get networking to work with this configuration anymore.

I configured this in the past with no issues, am I missing a step or is this a bug in 1.5?

I have fully updated my 1.5 installation.

Petrus4 · Jan 23, 2010

Here is the error I get when I try to start networking: (forgot to post it in my previous post)

Code:

# /etc/init.d/networking restart

 * Reconfiguring network interfaces...                                                                                                    eth0: ERROR while getting interface flags: No such device
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.

dietmar · Jan 24, 2010

Petrus4 said:
Here is the error I get when I try to start networking: (forgot to post it in my previous post)

How can I reproduce that bug?

There is related bug http://bugzilla.openvz.org/show_bug.cgi?id=478 - hopefully that will fix it.

Petrus4 · Jan 24, 2010

dietmar said:
How can I reproduce that bug?

There is related bug
http://bugzilla.openvz.org/show_bug.cgi?id=478 - hopefully
that will fix it.

Hi Dietmar,

To reproduce the bug:

Install ubuntu 8.04 template on openVZ container in Proxmox-VE 1.3
Install FOG package (Free open source ghost)
remove nfs-kernel-server package
Install nfs-user-server package

assign bridged network to this container via proxmox-gui and modify
/etc/network/interfaces with static ip, netmask, gatway etc.

At this point all works fine and the server has been in production as
an imaging server with no issues for many months.

Upgrade proxmox-ve to 1.4

Still no issues.

Upgrade to Proxmox-ve to version 1.5

network configuration disappears on this container.

What I tried:

Changed configuration to bridged mode for this container and assigned vmbr0
Saved it.
After refreshing the page the bridged mode goes back to disabled. (??)

I edited /etc/network/interfaces in the container to:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.10.2
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
gateway 192.168.10.1

restarted networking and get the following error:

# /etc/init.d/networking restart

* Reconfiguring network interfaces... eth0: ERROR while getting interface flags: No such device
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.

Tried to set bridged networking again in the GUI:

from Disabled to vmbr0 saved it and again these settings do not hold.

Have researched the openVZ forums / bugs for similar issues but though there is some info about debian based templates from 2008 I cannot find a good fix for this.

Not sure what to do next. Thanks.

Petrus

dietmar · Jan 25, 2010

Are you sure you use the latest version? Whats the output of

# pveversion -v

Petrus4 · Jan 25, 2010

dietmar said:
Are you sure you use the latest version? Whats the output of

# pveversion -v

# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-9-pve
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.24-9-pve: 2.6.24-18
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-8
vncterm: 0.9-2
vzctl: 3.0.23-1pve6
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

Petrus4 · Jan 25, 2010

please see previous post again.. I originally had the info from a different machine and now updated the post with the correct info.

seems this system did not update correctly. I have have run apt-get update and upgrade and no new updates are available.. what can I do to get the latest update?

Petrus4 · Jan 25, 2010

I changed to the following kernel: 2.6.18-1-pve to see if this would help but still not able to configure a bridged network in the container.

current pveversion -v

pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.18-1-pve
proxmox-ve-2.6.18: 1.5-4
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-8
vncterm: 0.9-2
vzctl: 3.0.23-1pve6
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-4

an anyone help with ideas on how I can bridged networking to work again in my containers?

Petrus4 · Jan 25, 2010

I ran a test on a new container. created it with bridged mode and it worked fine
(same kernel)

Then I removed the bridged mode went to venet with ip and saved.

Then removed venet and tried to configure veth again and I get the same issue.
the settings will not hold and eth0 keeps reverting to "disabled"

upgrade to 1.5 and no network on debian Appliances

New Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

New Member

Proxmox Staff Member

bleau69

Guest

Active Member

Proxmox Staff Member

bleau69

Guest

Active Member

Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Member

Member

Member

We value your privacy