Add all three of the following options to your QEMU command line:
-debugcon file:debug.log \
-global isa-debugcon.iobase=0x402 \
-serial stdio
In the OVMF debug log, you will see that your boot loader is launched:
[Bds]Booting UEFI QEMU DVD-ROM QM00003
FatDiskIo: Cache Page OutBound occurred!
FSOpen: Open '\EFI\BOOT\BOOTX64.EFI' Success
[Bds] DevicePath expand: PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0) -> PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0)/CDROM(0x1,0xC83AD,0x11C0)/\EFI\BOOT\BOOTX64.EFI
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 6C4D040
Loading driver at 0x00006486000 EntryPoint=0x000064A3000
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 700E318
And on the serial console, you will get the register dump for the crash:
!!!! X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - 00000000 !!!!
RIP - AFAFAFAFAFAFAFAF, CS - 0000000000000038, RFLAGS - 0000000000000206
ExceptionData - 0000000000000000
RAX - AFAFAFAFAFAFAFAF, RCX - 00000000070176A0, RDX - 00000000070176A0
RBX - 0000000006C4D018, RSP - 0000000007AFBA28, RBP - 0000000007AFBAE0
RSI - 0000000006534D9A, RDI - 0000000006485FBA
R8 - 0000000000000000, R9 - 0000000000000000, R10 - 0000000000000020
R11 - 00000000067E7180, R12 - 0000000000000000, R13 - 0000000006F883E8
R14 - 0000000006F883F0, R15 - 0000000007B1E9D0
DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030
GS - 0000000000000030, SS - 0000000000000030
CR0 - 0000000080000033, CR2 - 0000000000000000, CR3 - 0000000007A9A000
CR4 - 0000000000000668, CR8 - 0000000000000000
DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 0000000007A88698 0000000000000047, LDTR - 0000000000000000
IDTR - 0000000007442018 0000000000000FFF, TR - 0000000000000000
FXSAVE_STATE - 0000000007AFB680
The pattern AFAFAFAFAFAFAFAF is used to fill memory that's being freed,
for debugging purposes. So, your BOOTX64.EFI application dances fandango
on core.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1624096
Title:
yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
Status in debian-installer package in Ubuntu:
Confirmed
Bug description:
Sometime after August 25th (or so) something changed in the Yakkety
ISOs that make them no longer boot under QEMU in UEFI mode. However,
the ISOs do work fine still on the physical UEFI hardware I've tested
(3 different systems). I'm not sure about other VM solutions like
Virtual Box, etc., as I haven't tested under anything other than QEMU.
But under QEMU, UEFI mode installs are definitely broken.
You get stuck in the OVMF firmware with the following text on the
screen (see attached screenshot):
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
Thus far I've only tested with a Xenial host, so I'm not sure whether
this problem exists with a Yakkety host + Yakkety guest.
This problem also doesn't seem to be the result of any changes in QEMU
(and related) in Xenial. With a Xenial host, you can still do UEFI
mode installs fine under QEMU when the guest is using the 16.04.1
ISOs, and likewise when the guest is using the latest Xenial daily
(16.04.2 WIP) ISOs. So the problem seems to be only when using a
Yakkety guest in UEFI mode.
Note this problem effects both Yakkety desktop and server ISOs (when
installing under QEMU in UEFI mode).
Finally, on the off chance it might be helpful to anyone who comes
across this bug report, I wrote a blog post a while back on how to use
QEMU in UEFI mode on a Xenial (or newer) host:
http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial-
host-uefi-guest
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions