Hi Michael, A follow-up on this, we finally figured out a way to make virtio netdev naming persistent [0], so this will work again as of the next release. It's a shame we had to go back and forth on this, but I hope it does not cause you too much headaches.
Cheers, Tom [0]: <https://github.com/systemd/systemd/commit/54683f0f9b97a8f88aaf4fbb45b4d729057b101c> On Fri, Jul 4, 2014 at 1:31 AM, Tom Gundersen <t...@jklm.no> wrote: > On Fri, Jul 4, 2014 at 12:55 AM, Michael Marineau > <michael.marin...@coreos.com> wrote: >> Working on bumping to 215 over here in CoreOS land, but I've got a >> question regarding the removal of persistent device names for virtio >> devices since changing the network device names creates a difficult >> upgrade path from 212. The commit was: >> >> http://cgit.freedesktop.org/systemd/systemd/commit/?id=bf81e792f3c0aed54edf004c1c95cc6f6d81d0ee >> "udev: persistent naming - we cannot use virtio numbers as they are not >> stable" >> >> The commit doesn't say what the issue was, in what situations are the >> virtio numbers not stable? > > They suffer from the same problem as the ethX enumeration. In many > cases they appear to be stable (as drivers typically get loaded in the > same order etc), but there is nothing ensuring it, so we can't rely on > that. > > Cheers, > > Tom _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
