URGEND BIG PROBLEM: All Containers with veth no start after update Proxmx 3.3

[Virtualizer]

<sup>Dear,

I get this error: missing bridge parameter at</sup> /usr/sbin/vznetaddbr line 16.vzctl start 104
Starting container ...
Container is mounted
Setting CPU limit: 0
Setting CPU units: 4000
Setting CPUs: 4
Configure veth devices: veth104.0
missing bridge parameter at /usr/sbin/vznetaddbr line 16.
/usr/sbin/vznetcfg exited with error
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Killing container ...
Container was stopped
Container is unmounted

Configuration-File:



ONBOOT="yes"


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





# Secondary parameters
KMEMSIZE="3893362688:4283432960"
OOMGUARPAGES="0:unlimited"
PRIVVMPAGES="unlimited"
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="1946157056:2141192192"
LOCKEDPAGES="1045888"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="300"
PHYSPAGES="0:2091776"


# Disk quota parameters
DISKSPACE="157286400:157286400"
DISKINODES="16000000:17600000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"


# CPU fair sheduler parameter
CPUUNITS="4000"


OSTEMPLATE="debian-5.0-standard_5.0-2_i386"
HOSTNAME="confixx-server-name.xxx"
NAMESERVER="8.8.8.8 213.186.33.99"
SEARCHDOMAIN="searchdomain.xxx"
# MAC for forum little bit changed **
NETIF="ifname=eth0,mac=02:00:00:**:eb:71,host_ifname=veth110.0,host_mac=02:00:00:**:eb:72;ifname=eth1,mac=02:00:00:**:df:cd,host_ifname=veth110.1,host_mac=02:00:00:**:df:ce;ifname=eth2,mac=02:00:00:**:95:dd,host_ifname=veth110.2,host_mac=02:00:00:**:95:de;ifname=eth3,mac=02:00:00:**:0b:52,host_ifname=veth110.3,host_mac=02:00:00:**:0b:53"
SWAPPAGES="0"
CPUS="4"
IOPRIO="3"
BOOTORDER="10"
CPULIMIT="0"

 

[Virtualizer]

I have found the problem. Can been before the bridge must not been a parameter, from now on yes. So the line for the network configuration must been changed:

NETIF="ifname=eth0,mac=02:00:00:**:eb:71,host_ifna me=veth110.0,host_mac=02:00:00:**:eb:72,bridge=vmbr0;ifname=eth 1,mac=02:00:00:**:df:cd,host_ifname=veth110.1,host _mac=02:00:00:**:df:ce,bridge=vmbr0;ifname=eth2,mac=02:00:00:** :95:dd,host_ifname=veth110.2,host_mac=02:00:00:**: 95:de,bridge=vmbr0;ifname=eth3,mac=02:00:00:**:0b:52,host_ifnam e=veth110.3,host_mac=02:00:00:**:0b:53"

must only at the end of the interface-configuration insert the: ,bridge=vmbr0

Thanks and I hope I can help with this answer an other admin too

Regards

Detlef

 

[rmoglia]

I just entered on GUI Web Based interface edit vm network interface and save and works fine.

 

[Virtualizer]

Dear rmoglia,

this special configuration is only interessting when used with veth about to use a mac, expl. before for confixx! This is an old configuration but we have 3 servers with many clients on it, they will not change to new servers So about this, they must pay now every half year more ... and I hope one time we can shut of the old confixx servers . But after we upgrade the version of proxmox this 3 servers cant start and we had a short panic time!

I dont know that others use containers (CT) with veth and mac?! About I written the 2nd message about the solution!

But thanks for your reply

Detlef

 

[tin]

I just had this problem too. To help anyone else who's panicking (since this is the top result on Google for the error):

Go to the failing container's network settings in the web interface.
Double click the interface to edit it. Change something and OK, then go back and fix it.
If there's more than one interface, do them all (to be sure).
Start the container.
Do the same for every other failing container.

I'm not sure if you actually need to edit the interface settings to fix this - I just did it to ensure it did.

 

[Virtualizer]

Please read my own answer too (Message 2) !!!


Regards

Detlfe

 

[Virtualizer]

and other problem can been with firewall, why then the bridge expl. vmbr0 will change to vmbr0f !!!
When firewall ist activated, you must enter for all network interfaces too the firewall setting to on - let their on vmbr0,
but this will go in the container config-file vmbr0f, exmpl in /etc/pve/openvz/123.conf

Regards

Detlef

 

[spirit]

and other problem can been with firewall, why then the bridge expl. vmbr0 will change to vmbr0f !!!
When firewall ist activated, you must enter for all network interfaces too the firewall setting to on - let their on vmbr0,
but this will go in the container config-file vmbr0f, exmpl in /etc/pve/openvz/123.conf

Regards

Detlef

It's not a problem, when firewall is enable, you'll have "vmbr0f",

but interfaces will not be plugged on a bridge "vmbr0f" !

a special fw bridge is created, something like vmbr0----fwbr<vmid>i0------veth interface



About your problem:

missing bridge parameter at /usr/sbin/vznetaddbr line 16.
/usr/sbin/vznetcfg exited with error

We try to plug the veth interface to the defined bridge,
I'll check if we can simply don't try to do it, if bridge is not defined.

Can you make a bugreport on https://bugzilla.proxmox.com/ ?