Problem to assign vlan to vmbridge (Proxmox VE 6) / pve-bridge error 512

mensinck

Renowned Member
Oct 19, 2015
24
1
68
Kiel, germany
We do have the following problem.

Have a network setup with 3 vmbridge interfaces für different VLAN blocks. This is due to usage of ibm-Blades where we can not bond the nics.

The setup is working on the blades.

This is the interfaces file on the blades:


auto lo
iface lo inet loopback

iface enp26s0f0 inet manual

iface enp21s0f0 inet manual

iface enp21s0f1 inet manual

#iface enp26s0f1 inet manual

iface eno1 inet manual

iface eno2 inet manual

iface enp0s26f0u2c2 inet manual

auto bond0
iface bond0 inet static
bond_miimon 100
bond_downdelay 100
bond_updelay 100
bond_mode 802.3ad
slaves eno1 eno2
address 192.168.110.150
netmask 255.255.255.0

auto vmbr0
iface vmbr0 inet static
address 192.168.120.150
netmask 255.255.255.0
gateway 192.168.120.220
bridge_ports enp21s0f0
bridge_stp off
bridge_fd 0


# bridge for VLANS 5,6,8,100
auto vmbr1
iface vmbr1 inet static
address 0.0.0.0
bridge_ports enp21s0f1
bridge_stp off
bridge_fd 0


# bridge for VLANS 15,121
auto vmbr2
iface vmbr2 inet static
address 0.0.0.0
bridge_ports enp26s0f0
bridge_stp off
bridge_fd 0


# Corosync Network
auto enp26s0f1
iface enp26s0f1 inet static
address 192.168.111.150
netmask 255.255.255.0


We additionaly have a ,,old" DL570 G5 as ,,Storage" host for ceph.

On this we have this network setup to have the same vmbrX interfaces to be able to move VM's to the host.

By the way, this machine has some probles with systemd interface naming (renameX interfaces).

We tried to use NamePolicy = mac in systemd/network.

But the we can not assign vlans to vmbrX interfaces.

The error is:

error: argument "enx002655e8aa6a.100" is wrong: "name" not a valid ifname
can't add vlan tag 100 to interface enx002655e8aa6a
kvm: network script /var/lib/qemu-server/pve-bridge failed with status 512



We also tried to use fixed names forthe interfaces with no success.

Any hints how to reolve this.

This is what we use:

proxmox-ve: 6.0-2 (running kernel: 5.0.21-3-pve)
pve-manager: 6.0-9 (running version: 6.0-9/508dcee0)
pve-kernel-5.0: 6.0-9
pve-kernel-helper: 6.0-9
pve-kernel-5.0.21-3-pve: 5.0.21-7
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.4-pve1
ceph-fuse: 14.2.4-pve1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-5
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-65
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-7
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-9
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve1


Regards Lukas
 
We tried to use NamePolicy = mac in systemd/network.
Is that node running Proxmox VE? I would assume not, as Proxmox VE doesn't use networkd.

error: argument "enx002655e8aa6a.100" is wrong: "name" not a valid ifname
can't add vlan tag 100 to interface enx002655e8aa6a
kvm: network script /var/lib/qemu-server/pve-bridge failed with status 512
This could be an issue with the length of the interface name, that throws ifupdown off.
 
Is that node running Proxmox VE? I would assume not, as Proxmox VE doesn't use networkd.
Yes this is on a host new installed from Proxmox VE Iso. After that we found interfaces named like ,,rename6" on a 4 port HP-network card.

Setting .link files is /etc/systemd/network and updating initramfs solved this.
An yes, systemd is not used by proxmox, so we also could not set interface names using other NamePolicy settings.


This could be an issue with the length of the interface name, that throws ifupdown off.

That was what I expected. We did work around this issue now by using ,,not renamed" interfaces for vmbrX network interfaces.

Using the renamed interfaces for the storage bond and corosync is working fine.

Regards Lukas
 
Yes this is on a host new installed from Proxmox VE Iso. After that we found interfaces named like ,,rename6" on a 4 port HP-network card.
Maybe a issue with udev not renaming the interface.
 
Maybe a issue with udev not renaming the interface.
You are right. udev is the problem here.

So net.ifnames=0 as grub boot parameter leads to old ethx interface names and everything is working fine.

But the naming scheme mentioned in the doku ,,wiki/Network_Configuration" :

.....
We currently use the following naming conventions for device names:

  • Ethernet devices: en*, systemd network interface names. This naming scheme is used for new Proxmox VE installations since version 5.0.
.....

is not valid for enx* mac based naming.

This in mind, we could close the tread.

Thanks Lukas
 
  • Like
Reactions: Roger_cwb
Hi, I'm having exactly the same issue, after assigning VLAN ID=112 to one of the VMs the VM refuses to start:
Code:
Error: argument "enx4865ee1606c9.112" is wrong: "name" not a valid ifname
can't add vlan tag 112 to interface enx4865ee1606c9
kvm: network script /var/lib/qemu-server/pve-bridge failed with status 512

Can someone please give me a hint how did you make it work?

I'm not as skilled in PVE so far so non-renaming interfaces and grub parameters don't tell me much, sorry :(
 
Thanks @spirit, the most straightforward answer so far!

1) Regarding renaming of the network interface, I don't have any file in /etc/systemd/network, should I create one and put this into its contents?

[Match]
MACAddress=01:23:45:67:89:ab # my mac address
[Link]
Name=lan0 # any short name?

Should I change anything on existing VMs, restart Proxmox, etc.?

2) Regarding using a VLAN aware bridge, are there any negative side-effects of this? I read that all VMs are assigned a distinct VLAN ID therefore they cannot communicate with each other, if I am right?

Thanks!
 
Thanks @spirit, the most straightforward answer so far!

1) Regarding renaming of the network interface, I don't have any file in /etc/systemd/network, should I create one and put this into its contents?

[Match]
MACAddress=01:23:45:67:89:ab # my mac address
[Link]
Name=lan0 # any short name?
yes, any shortname
Should I change anything on existing VMs, restart Proxmox, etc.?
no change in the vm, update /etc/network/interfaces vmbrX to use "lan0" instead enx4865ee1606c9, reboot

2) Regarding using a VLAN aware bridge, are there any negative side-effects of this? I read that all VMs are assigned a distinct VLAN ID therefore they cannot communicate with each other, if I am right?
if you enable vlan-aware bridge, the vm without vlan tag, will be tagged with default vlan1 (so, you need to check in your physical switch if it's also tagging default vlan1)
 
I'm still scared doing this since I don't want to screw up my networking :( Maybe I move physically to the machine over the weekend.

I think that this should be handled somehow by the Proxmox VE (i.e. it shouldn't create longer network if names than acceptable by Linux/Debian). Can I file a bug report via this forum?

Thx.
 
For those who might run into the same problem, I confirm that the VLAN aware bridge worked for me. This is what I did:

1) WebUI -> DataCenter -> node (proxmox) -> System -> Network -> vmbr0 -> VLAN aware -> OK

1589119712376.png

2) Reboot proxmox

3) Stop VM

4) VM -> Hardware -> Network -> Edit -> VLAN ID: 100

5) Start VM

Works well :)

Another HUGE advantage of the VLAN aware bridge is that you can assign / remove / change the VLAN ID on the fly, without stopping the VM (as I did above).
 

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!

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!