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
"eno1636". 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
@Haw: see comment #3.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1550539
Title:
VMWare network interface name change with xenial upgrade
Status in systemd package in
| [1.939106] e1000 :02:00.0 ens32: renamed from eth0
That would be because udev v197 and above now uses predictable network
interface names by default[1]. The upgrade process should probably add
net.ifnames=0 on the kernel command lin or update /e/n/i.
[1]http://www.freedesktop.org/wiki/S
Hi,
I don't have anything in /etc/udev/rules.d
# ls -al /etc/udev/rules.d/
total 8
drwxr-xr-x 2 root root 4096 Oct 15 08:01 .
drwxr-xr-x 4 root root 4096 Feb 26 02:54 ..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1550539
Title:
VMWare network interface name change with xe
Note to myself: We already have this logic for upgrading virtualized
hosts:
# we enabled net.ifnames in 220-7 by default; don't change iface names in
# virtualized envs (where 75-persistent-net-generator.rules didn't work)
if dpkg --compare-versions "$2" lt-nl "220-7~" &&
[ ! -e /etc/ud
6 matches
Mail list logo
