[libvirt] [PATCH] openvz: swap <source bridge=...> with <target dev=...>

Daniel P. Berrange berrange at redhat.com
Tue Sep 30 14:10:14 UTC 2008

On Tue, Sep 30, 2008 at 05:57:20PM +0400, Anton Protopopov wrote:
> >
> > 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?

Start from vnet0 and look for the first available name.

> >
> > 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.

The interface name inside the container is not something that is expressed
in the libvirt XML. That is left upto the guest OS to decide, and not 
something libvirt needs to care about.

We only care about configuration from the host side.

|: 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 :|

More information about the libvir-list mailing list