[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1089006
Title:
Qemu scramb
Is there still something left to do here, or could we close this bug
nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1089006
Title:
Qem
For the benefit of 1) others and 2) me when I forget how this works-
I did find a solution in formatting the xml file.
If you leave the vnets out completely, see file below, the generic xml file
will cooperate with libvirt and qemu and
order the VM's eth devices as they are ordered on the hyper
Thank you Daniel.
I understand what you say and agree. However when presented with a mapping and
an order by libvirt, shouldn't the order be preserved by default? If the OS
scrambles it, then fine, not your problem...
Are we on the right track here, is there some way to control the order
as pres
There is really no such concept as "NIC order" at the hardware level in
QEMU. NIC naming order is something that operating systems invent
according to some policy they have. As far as libvirt & QEMU are
concerned, you only have control over the PCI device slot numbering.
The operating system may ch
