[SOLVED] After upgrading to 7.2-14 on starting VM's error dev tap104i0 master static' failed: exit code 255 when OVS is used

M

mackpaul1967

Renowned Member
Mar 9, 2011
17
1
68
After upgrading

Some of my VMs get the below error when Migrating or starting up. On migration, they stay in the paused state but they say running with qm list. On startup they still work with no issues other than this error on startup.

TASK ERROR: command '/sbin/bridge fdb append 36:63:36:37:61:30 dev tap104i0 master static' failed: exit code 255

i can remove the Network Device and add it back and it will start or migrate without errors a few times then I will get the above error.

on some of my VM's I have no issue at all.

using openvswitch:

root@pve-02:~# pveversion --verbose
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-14 (running version: 7.2-14/65898fbc)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-7
libpve-guest-common-perl: 4.2-2
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.2
pve-cluster: 7.2-3
pve-container: 4.3-4
pve-docs: 7.2-3
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.1.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-10
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
 
  • Like
Reactions: kam821
Same issue here. One observation: If Firewall on the interface is set to Yes it works for my containers(CentOS, Debian), if set to No --> error as reported above.
 
With firewall enabled there's a standard Linux bridge plugged in between the virtual guest, at which point the bridge fdb append command works again. We need to handle OVS more explicitly for the code added to support the disable-mac-learning feature.
 
Hello, same problem,

With firewall enabled or disabled at datacenter level or/and node level


Error on all virtual machine at start :
RTNETLINK answers: Operation not supported
TASK ERROR: command '/sbin/bridge fdb append XX:XX:XX:XX:XX:XX dev tapXXXi1 master static' failed: exit code 255


Configuration :
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-15 (running version: 7.2-15/963997e8)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-2-pve: 5.15.60-2
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-7
libpve-guest-common-perl: 4.2-2
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
 
  • Like
Reactions: kam821
also PBS is complaining when backing up stopped VMs or templates for this reason
9001ci-ubuntu-imageFAILED00:00:01command '/sbin/bridge fdb append XX dev tap9001i0 master static' failed: exit code 255
9002focal-base-202201FAILED00:00:01command '/sbin/bridge fdb append XX dev tap9002i0 master static' failed: exit code 255
9003ubuntu-20.04.3FAILED00:00:02command '/sbin/bridge fdb append XX dev tap9003i0 master static' failed: exit code 255
9010jammy-cloudinitFAILED00:00:02command '/sbin/bridge fdb append XX dev tap9010i0 master static' failed: exit code 255
9011jammy-base-202208FAILED00:00:01command '/sbin/bridge fdb append XX dev tap9011i0 master static' failed: exit code 255
 
Last edited:
gzannella said:
With firewall enabled or disabled at datacenter level or/and node level
Click to expand...
Node level does nothing for virtual guests, you rather need to ensure that the guest and its vNICs also have it enabled (separate options).

Anyhow, there are a new set of packages trying to address this issue available on the pvetest repository:

libpve-common-perl version 7.2-8
pve-container version 4.3-6
qemu-server version 7.2-11

feedback would be appreciated (ensure to reload the GUI after updating to these version to avoid having the start done by an left-over old API worker).
 
  • Like
Reactions: ruy, JameZUK and mackpaul1967
just did a quick test with testing packages and shutdown / restart successfully one Node without any issue. Also a backup works now again.
 
Last edited:
  • Like
Reactions: mackpaul1967
t.lamprecht said:
Node level does nothing for virtual guests, you rather need to ensure that the guest and its vNICs also have it enabled (separate options).

Anyhow, there are a new set of packages trying to address this issue available on the pvetest repository:

libpve-common-perl version 7.2-8
pve-container version 4.3-6
qemu-server version 7.2-11

feedback would be appreciated (ensure to reload the GUI after updating to these version to avoid having the start done by an left-over old API worker).
Click to expand...
My preliminary testing seems to be working. Awesome turnaround. I will do some more testing and report back with any issues.
 
t.lamprecht said:
Ack, due to the positive feedback here (thanks!) and as not much changed in those package's we'll move them to no-subscription pretty soon.
Click to expand...
Confirmed. Works with pve-container version 4.4-2. Could someone change the title to solved. Thanks!
 
Hello all,

i have just upgraded to proxmox 7.3, but the error still persists.

Package versions:

Code: 
proxmox-ve: 7.3-1 (running kernel: 5.15.64-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-5.19: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.19.17-1-pve: 5.19.17-1
pve-kernel-5.19.7-2-pve: 5.19.7-2
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
ceph: 15.2.17-pve1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: not correctly installed
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-8
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-network-perl: 0.7.2
libpve-storage-perl: 7.2-12
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

I use ovs and have proxmox firewall enabled only on host.

The error i get when i turn on every vm is this:

RTNETLINK answers: Operation not supported
TASK ERROR: command '/sbin/bridge fdb append XX:XX:XX:XX:XX:XX dev tapXXXi0 master static' failed: exit code 255
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back