Bug#799253: virtio ens3 network interface

[Martin Pitt]

Hey Harald,

Harald Dunkel [2015-09-17 20:02 +0200]:
> > In such a scenario you can already not rely on stable interface names, as they would change with the changing hardware (unless you have an existing 70-persistent-net-names.rules from jessie, then it's okay again).
> > 
> 
> 70-persistent-net-names.rules was reset in /etc/rc.local at boot
> time (after eth0, eth1 etc were assigned and configured). Previous
> boot sessions were ignored.

Ah, I see. With the current naming system you have to disable the
predictable names differerently now, either by booting with
net.ifnames=0 or by creating an empty
/etc/udev/rules.d/80-net-setup-link.rules or (more elegantly/reliably)
set different name(s) in some /etc/systemd/network/*.link file (see
man systemd.link).

> > It is a different case because the upstream change in question specifically applies to virtio_net devices only.
> > 
> 
> Now I have the impression that upstream created bad code, and you
> tried to work around this. Is this the case?

It's not bad code -- it's right going forward, for new installations.
But while it's a bug fix, it breaks existing installations which is
why in general we need to keep the previous (unstable) names on
upgrades.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)