Red Hat Bugzilla – Bug 486575
Ignores 'target dev=...' attribute in network devices
Last modified: 2009-12-02 08:00:37 EST
Description of problem:
libvirt seems to ignore the name given in <target dev='...'> statements. E.g. when following documentation and adding a
network device to a qemu-kvm domain, the resulting interface is 'vnet0' (or the first available one), but not 'vnet101' as requested.
Predictable interface names are essential as they are used in firewall rules.
Version-Release number of selected component (if applicable):
This is intentional, see:
> Hang about though, don't we sometimes want to explicitly set the name of
> some interfaces to vnetXXX?
No, if you want to manually set interface names, you have to use something
other than a 'vnet' prefix. 'vnet' is the prefix for auto-generated names
in same way as 'vif' is the prefix for Xen auto-generated names.
As Mark says this is intentionale, but we should probably update the domain XML documentation to mention the reserved prefixes.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
As per comment #2, there are now explicit docs for this upstream:
So closing this bug as UPSTREAM.