I installed VMWare player and compared a wily and a xenial installation. On xenial I indeed get "ens33", while on wily I get a rather bad name "eno16777736". You did not mention the old name of the ethernet interface, but can you confirm that this was a wily *install* (as opposed to an upgrade from an earlier release), and that the old name was *not* eth0, but "eno16777736" or similar? Then indeed the migration to ifnames does not apply as wily already used ifnames.
This naming was fixed in https://github.com/systemd/systemd/commit/6c1e69f9 by ignoring interface indexes that the BIOS reported that are implausibly high (as VMWare does that for some reason). We do know the slot-based names that are being used since the above commit so we could attempt to auto-fix at least /etc/network/interfaces in postinst. However, we can't fix possible other places where the previous name is being used, so perhaps the safest approach would be to document this in the release notes and in NEWS. ** Summary changed: - VMWare network interface name change with xenial upgrade + VMWare network interface name change with wily → xenial upgrade ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550539 Title: VMWare network interface name change with wily → xenial upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1550539/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
