With commit cdbe657809ffcc460424640e9c55f37cd3e2f24d (from meta-agl) the VMDK can no longer be booted directly using the `-hda` parameter.

I get the following when trying to use OVMF:

BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM00003 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found
BdsDxe: failed to load Boot0002 "UEFI QEMU HARDDISK QM00001 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0): Not Found

OVMF would require a efi boot stub (although kernel loading seems to work directly, and there is a loader.conf generated)

Directory of: FS0:\EFI\BOOT\
01/29/2020  13:56 <DIR>         2,048  .
01/29/2020  13:56 <DIR>         2,048  ..
          0 File(s)           0 bytes
          2 Dir(s)

Maybe this is because it is using systemd-boot?

I'm not really sure this is actually an issue/bug, and maybe the wiki has to be documented to use -kernel instead, in the case of booting with qemu. I haven't tried using vbox or anything else.