http://bugzilla.suse.com/show_bug.cgi?id=989462 http://bugzilla.suse.com/show_bug.cgi?id=989462#c4 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glin@suse.com --- Comment #4 from James Fehlig <jfehlig@suse.com> --- (In reply to Alan Ott from comment #3)
My bug is that it _can_ find the firmware (because it shows in the virt-manager GUI) but it uses the wrong <loader ... type=""> in the generated XML file. It's trying to use "<loader ... type='pflash'>", but the only thing that seems to work is "<loader ... type='rom'>".
But as you already noted, the type _should_ be pflash. Perhaps there is a problem with qemu, or the firmware blob. FYI, you can get debug info from ovmf by adding the following to your guest XML <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> ... <qemu:commandline> <qemu:arg value='-debugcon'/> <qemu:arg value='file:/tmp/ovmf-debug.log'/> <qemu:arg value='-global'/> <qemu:arg value='isa-debugcon.iobase=0x402'/> </qemu:commandline> ... </domain> Also, is there anything interesting in the VM's log file (/var/log/libvirt/qemu/<vm-name>.log? It would be good to verify libvirt created a correct qemu command line, although I think it did given the info you provided in #0. BTW, bug#983747 is essentially a SLE clone of bug#981836. -- You are receiving this mail because: You are on the CC list for the bug.