Closed ElvishJerricco closed 5 years ago
It's your OVMF. Here's what I get with the last official OVMF binary from https://sourceforge.net/projects/edk2/files/OVMF/ against a gnu-efi Debian 9.6 hfs_x64.efi
:
@pbatard Not sure what I did, but it's loading now. FWIW, the README on that site says:
The Latest releases are now hosted on Github: https://github.com/tianocore
Though I can't find binary releases there
Yes, the source had moved, but the last official OVMF binaries are still on SF, and, where possible, I prefer to validate against official binaries as this reduces the headaches (which you have experienced) of introducing one's own issues through one's build process. With EfiFs being a side project for which I can devote only very limited time compared to my other projects, I have exactly zero incentive to figure out the many ways in which things can break from trying to use the very latest of everything.
Running OVMF in qemu, going to the UEFI Shell, and entering
load hfs_x64.efi
yieldsImage 'hfs_x64.efi' is not an image.
I'm not sure whether it's OVMF or EfiFs at fault, but the other EfiFs drivers that I've tried have worked so I'm assuming it's EfiFs. Both OVMF and EfiFs were built with both their latest releases and their latest commits onmaster
.Are there tools I can use to try and debug this?