[libvirt] Re: Overriding vnetN with the <target> element in xml configuration not working

[Ahmed Medhat]

Well,

I don't recall reading this constrain anywhere in the documentation !


/*
|| Thanks, Ahmed Medhat
|| ultimatetux [at] gmail [dot] com
|| +2-012-4184768
|| Impossible is not a fact, It's an opinion!
*/



On Mon, Sep 29, 2008 at 11:30 AM, Daniel P. Berrange
<berrange at redhat.com> wrote:
> On Sat, Sep 27, 2008 at 02:58:14AM +0200, Ahmed Medhat wrote:
>> Ok, so its kinda creepy now, it works with change the device name to
>> anything but vnetN.
>
> vnetNNN is an automatically generated device name pattern. We explicitly
> ignore any requested target dev with that naming pattern because manually
> specified name will almost certainly clash with an auto-generated one and
> cause the domain to fail to start.
>
> The same applies for 'vifNNNN' naming
>
>> This is what did work with me..
>>
>>     <interface type='bridge'>
>>       <source bridge='virbr0'/>
>>       <target dev="vn01"/>
>>       <mac address='00:16:3e:6c:1f:9d'/>
>>     </interface>
>>
>> This must be something with libvirtd code handling this specific
>> element directive.
>>
>> I will wait for someone to do any input for a while then fire up a bug report.
>
> It isn't a bug - it is delibrate.
>
> 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 :|
>