Possibly, though its not terribly consistent so far.
Xen - vifNNN.MMM (NNN dom ID, MMM = nic number)
QEMU - vnetNNN (NNN = global host nic number)
LXC - vethNNN (MMM = global host nic number)
And how these drivers choose NNN? Do QEMU driver and LXC driver use the same
NNN?
NNN?
We can't change the format Xen uses, but it could be desirable to make
LXC, QEMU and OpenVZ all use vnetNNN scheme by default for auto assigned
nics names on the host side.
Now openvz driver chooses not interface name in host, but interface name in container.
(If you specify contaner-ifname, say, vnet4, you get host-ifname veth$veid.4.)
So first we need to decide: is container-ifname derivative from host-ifname or vice versa :)
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
-- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list