VM Network interface name changed after migration from other hypervisor

[kakuni]

Hi,
I am migrating to Proxmox VE many VMs that are running on Hyper-V.
Most of these are UEFI-booted Ubuntu VMs and the name of their network interface is a string like eth0.
After migrating them, the network interface name was changed to a string like enp6s18.
And the interface configuration was made inoperative.

There are several naming methods, and I believe that it is guest OS and its configuration that decides which one to use.
Why would replacing the hypervisor have an impact on that?

Also, it is very annoying to modify the settings of multiple VMs one by one,
so is there any way to reduce these unwanted effects all at once?

Thank you in advance.

 

[bbgeek17]

There are several naming methods, and I believe that it is guest OS and its configuration that decides which one to use.

You are correct, its the Guest OS that is responsible for the name.

Why would replacing the hypervisor have an impact on that?

Because each hypervisor handles the hardware differently. Many things change: PCI connectivity, model, bios, firmware. The Kernel takes it all into consideration when it comes up with a name: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

Also, it is very annoying to modify the settings of multiple VMs one by one,
so is there any way to reduce these unwanted effects all at once?

One possibility is to make modifications prior to migration. There could be a few avenues: simply clone the config to predicted name, implement udev rules to match on MAC and ensure that MAC is stable, few other paths.
Each one requires manual intervention. The value of finding a workaround really depends on how many VMs you are moving. You will spend time on this task either way.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[yuvalattar]

You are correct, its the Guest OS that is responsible for the name.

Because each hypervisor handles the hardware differently. Many things change: PCI connectivity, model, bios, firmware. The Kernel takes it all into consideration when it comes up with a name: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

One possibility is to make modifications prior to migration. There could be a few avenues: simply clone the config to predicted name, implement udev rules to match on MAC and ensure that MAC is stable, few other paths.
Each one requires manual intervention. The value of finding a workaround really depends on how many VMs you are moving. You will spend time on this task either way.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi ,
did you happen to find a solution for that issue ?

thanks .

 

[bbgeek17]

Hi ,
did you happen to find a solution for that issue ?

In Linux you can create a custom name using a consistent identifier, ie MAC. You could utilize Udev rules for that.
https://unix.stackexchange.com/questions/91085/udev-renaming-my-network-interface

You'd want to switch to this name in your configuration and test it _before_ migration.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox