Displaying 3 results from an estimated 3 matches for "desired_dev_name".
2017 Jan 14
2
Controlling the name of the 'tap0' device, in a bridged networking setup
...configuration
<interface type='bridge'>
<source bridge='br0'/>
</interface>
The libvirt documentation (
http://libvirt.org/formatdomain.html#elementsNICSBridge) and other
discussions online tell me that I just need to include the <target
dev='desired_dev_name'/> tag in the XML specification of the domain under
the <interface> tag. Unfortunately doing so appears to have no effect; the
tun device created and 'enslaved' in the bridge is still called 'tap0'.
Interestingly, I never get a tun device with a name prefixed by 'vn...
2017 Jan 20
2
Re: Controlling the name of the 'tap0' device, in a bridged networking setup
...;>
>> <source bridge='br0'/>
>> </interface>
>>
>> The libvirt documentation (http://libvirt.org/formatdoma
>> in.html#elementsNICSBridge) and other discussions online tell me that I
>> just need to include the <target dev='desired_dev_name'/> tag in the XML
>> specification of the domain under the <interface> tag. Unfortunately doing
>> so appears to have no effect; the tun device created and 'enslaved' in the
>> bridge is still called 'tap0'. Interestingly, I never get a tun device with...
2017 Jan 17
0
Re: Controlling the name of the 'tap0' device, in a bridged networking setup
...e='bridge'>
> <source bridge='br0'/>
> </interface>
>
> The libvirt documentation
> (http://libvirt.org/formatdomain.html#elementsNICSBridge) and other
> discussions online tell me that I just need to include the <target
> dev='desired_dev_name'/> tag in the XML specification of the domain
> under the <interface> tag. Unfortunately doing so appears to have no
> effect; the tun device created and 'enslaved' in the bridge is still
> called 'tap0'. Interestingly, I never get a tun device with a name...