On Thu, Dec 06, 2012 at 01:12:52PM +0200, Michael S. Tsirkin wrote:
On Wed, Dec 05, 2012 at 03:51:39PM +0200, Dan Kenigsberg wrote:
On Tue, Dec 04, 2012 at 05:25:48AM -0500, Alon Bar-Lev wrote:
Thanks for this verbose description.
I don't think using libguestfs is the solution for this.
Yeah, it seems like a hack that would be quite hard to maintain for all supported guest operating systems.
Fixing qemu to accept BIOS interface name at -net parameter is preferable. I don't think we should expose the interface a PCI device as it will have some drawbacks, but attempt to use the onboard convention.
I don't see a real use case for setting the bios name explicitly. After all, libvirt/vdsm/Engine is going to to allocate them according to their relative order. I'd be content with qemu providing a sane, reproducible, biosdevname for each nic.
Michael, would it be difficult to have?
This is not a qemu issue. This is a biosdevname/VMware issue. biodevname has this code:
/* Algorithm suggested by: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd... */
static int running_in_virtual_machine (void) { u_int32_t eax=1U, ecx=0U;
ecx = cpuid (eax, ecx); if (ecx & 0x80000000U) return 1; return 0;
}
So it just looks for a hypervisor.
It should look at the hypervisor leaf and either blacklist vmware specifically or whitelist kvm.
Please open (preferably urgent prio) bugzilla for biosdevname component so we can fix it in F18, cc me. I can write you a patch but maintainer needs to apply it.
Thanks for the analysis, Michael. Fedora bug opened: Bug 884990 - non deterministic bios dev naming in KVM guests