[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [libvirt] invoking interface.script - missing interface name of domain



Hi Daniel,

within the latest CVS checkout, the problem below is not
fixed. It there an open bug (to track) in redhat bugzilla for it ?
If not, should I create one ?

regards
Danny


> On Tue, Jan 20, 2009 at 04:44:22PM +0100, Daniel Schwager wrote:
> > > QEMU is responsible for passing arguments to the interface
scripts,
> > > so its out of libvirt's control. QEMU passes a single paramter to
> > > the script, which is the name of the TAP device interface being
> > > added.  If you don't give a <target dev='tap3'> libvirt generates
> > > a TAP device name vnetXXXX.
> >
> > If I do not specify the <target>-element inside of <interface>,
> > your docu told me
> >
> > 	"The guest will have a tun device created with a name of vnetN,
> > which can also be overridden with the <target> element."
> > 	(http://www.libvirt.org/formatdomain.html#elementsNICS)
> >

> That is a bug I'm afraid - it *should* pass the real auto-generated
> interface name but for some reason it isn't. I see this is one of the
> XML configs we don't have tested in our xml -> ARGV conversion test.
> 
...
> Daniel




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]