He's also should be able to attach just the .efi file or install graphics drivers via qxl. <div class="gmail_quote">On Apr 11, 2016 6:48 PM, "Laszlo Ersek" <<a href="mailto:lersek@redhat.com">lersek@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 04/10/16 16:46, Blank Field wrote: > What you can do - convert libvirt xml into a usual qemu command line, > and add an ISA debug console and check OVMF debug output in it. * Yes, capturing the OVMF debug log should be the first step when reporting apparent OVMF issues. You can get that log without resorting to the raw QEMU command line. Modify your domain XML like this: - add the following attribute to the root element of the domain XML: <domain type='kvm' xmlns:qemu='<a href="http://libvirt.org/schemas/domain/qemu/1.0" rel="noreferrer" target="_blank">http://libvirt.org/schemas/domain/qemu/1.0</a>' <-- this one > - add the following XML fragment near the end of the domain XML, as a direct child of the <domain> element: <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='isa-debugcon.iobase=0x402'/> <qemu:arg value='-debugcon'/> <qemu:arg value='file:/tmp/guest_name.log'/> </qemu:commandline> This will send the OVMF log to "/tmp/guest_name.log". * Regarding the specific case: a UEFI oprom for a GPU may easily be buggy even if it matches the card. If you are experimenting with "similar" drivers, all bets are off. Please buy a decent card (Alex has recommended the GTX750 several times; I myself bought one on his recommendation, and have had zero problems with it). Or else, at least get an officially supported driver binary from the manufacturer, please. Thanks Laszlo </blockquote></div>