On Wed, Oct 01, 2008 at 10:33:49AM +0400, Anton Protopopov wrote: > 2008/9/30 Daniel P. Berrange <berrange@xxxxxxxxxx> > > > On Tue, Sep 30, 2008 at 05:57:20PM +0400, Anton Protopopov wrote: > > > > > > 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. > > > In OpenVZ case you _must_ to decide what name the > interface will have inside the container. The command line for ading an > interface in OpenVZ looks like > # vzctl set $veid --ifname_add ifname[mac, host_ifname, host_mac] > The only mandatory field is the name of _container interface_ If openvz kernel requries specification of a NIC name for inside the container, then this is an implemntation detail that the libvirt OpenVZ driver will have to deal with. It can auto-assign them to be eth0, eth1, etc. This is not exposed in the libvirt XML though, since it is not relevant to the host admin, only apps inside the guest. > * absolutely ignore the <target dev=".."> in openvz XML description As I said before this needs to reflect the name of the interface on the host side. It can be ignored when creating a guest, since for the majority of uses cases it can be safely auto-generated. It must be filled in when dumping XML for a guest, so the host admin knows which NIC in the host corresponds to the guest. 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