To further troubleshoot this, it would be interesting to see the output of what udevadm thinks about these interfaces:
E.g. output of: $ udevadm info -p /sys/class/net/eth0 and $ udevadm info -p /sys/class/net/enp0s3 For the BIOS / UEFI case. Note that changing the boot type from bios to uefi on the fly is not that well support, as different sets of packages are installed / expected to be available by BIOS vs UEFI installations. In general, udevd has been disabling persisten interface naming for the virtual machines due to instability of those interfaces. But it is interesting that "stable" names are picked for the UEFI case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695089 Title: Network Interface names differ between BIOS / UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1695089/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
