persistent network interface failed

[god]

I've added net.ifnames=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, run sudo update-grub, removed /etc/udev/rules.d/70-persistent-net.rules but after reboot I still got eth0 interface which according to dmesg was renamed from veth9JEDKK (this ubunte-server 15.04 is installed in ovirt cluster).

How can I avoid this renaming? What exactly causing this? Are there some leftovers in addition to 70-persistent-net.rules interfere?

I don't want ubuntu's udev to be creative about interface naming, especially in potentially race-prone manner. What I want is the default upstream udev scheme described in http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ - the less ubuntu differs from other GNU/Linux, the easier it would be to maintain.

[Martin Pitt (pitti)]

Does that still happen if you move away /lib/udev/rules.d/75-persistent-net-generator.rules? It should be inert with net.ifnames=1, but can you please give the output of "cat /proc/cmdline" to be sure that it actually made it there?

[god (humper)]

 cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=f4862d1a-ebc5-4bfd-a3f1-e42a1ab40f2b ro net.ifnames=1

[god (humper)]

ls /lib/udev/rules.d/|grep 75
75-net-description.rules
75-probe_mtd.rules
75-tty-description.rules

[god (humper)]

And still - the interfaces are named eth0, eth1 etc. Surprisingly on another machine modifying kernel command line and killing udev rules from /etc were sufficient to get rid of this renaming. Are there some more places this creeped into?

[Martin Pitt (pitti)]

veth interfaces aren't covered by persistent names anyway, as you determine their name when you create them. What are you trying to do exactly and how do you create the veth device pair?

[god (humper)]

Ah, my bad, didn't realized that virtio actually names interfaces that way.