[SOLVED] Migration failed: can't add vlan tag to interface

Dec 26, 2018
138
2
23
35
It's only migrating a VM with vlan tag 50, to this Proxmox node.

Migrating from:

task started by HA resource agent
2020-09-01 12:58:53 starting migration of VM 100 to node 'proxmox4' (10.0.0.14)
2020-09-01 12:58:53 starting VM 100 on remote node 'proxmox4'
2020-09-01 12:58:55 [proxmox4] Error: 8021q: VLAN device already exists.
2020-09-01 12:58:55 [proxmox4] can't add vlan tag 50 to interface bond0
2020-09-01 12:58:55 [proxmox4] kvm: network script /var/lib/qemu-server/pve-bridge failed with status 512
2020-09-01 12:58:55 [proxmox4] start failed: QEMU exited with code 1
2020-09-01 12:58:55 ERROR: online migrate failure - remote command failed with exit code 255
2020-09-01 12:58:55 aborting phase 2 - cleanup resources
2020-09-01 12:58:55 migrate_cancel
2020-09-01 12:58:56 ERROR: migration finished with problems (duration 00:00:03)
TASK ERROR: migration problems

Migrating to:
QEMU: Error: 8021q: VLAN device already exists.
QEMU: can't add vlan tag 50 to interface bond0
QEMU: kvm: network script /var/lib/qemu-server/pve-bridge failed with status 512

TASK ERROR: start failed: QEMU exited with code 1
 
Some problem with one of the network cards had been renamed to "rename2", and lost link in the process.
A reboot of the server solved the issue.
It has a dual gigabit ethernet in bonding mode, that is PCIe. This is because the server has dual 10gbit integrated.
 

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!