![]() ![]() Removing one of the default DXE driver doesn't make it hang, adding it back doesn't make QEMU hang either.įor logs to be written with -D, I also have to provide a -d item, where item is one of -d help, such as int for interrupts. 3 - Build OVMF myself, adding my driver natively 4 - Any other suggestion?Īny help with my previous attempts would also be kindly appreciatted. This question says that OVMF_CODE.fd allows secure boot to be comprised, but I haven't been able to find a OVMF_CODE file. Further attempts 1 - Find out how to get QEMU logs 2 - Find out how to disable secure boot But I haven't been able to understand how to do that yet. If I manage to get the vanilla version working I'd then add my driver natively. I tried to build OMVF.fd with edk2, but the build has errors. This is not allowing the modified firmware image to run. If I had to pick a reason, I'd say that secure boot is enabled. I have also tried to hook gdb to QEMU with the -S -s flags, but looking at assembly didn't help me understand what is failing. I have tried to use -D log.txt, but no logs are written. Unfortunately, when I try to boot that bios with QEMU, the system hangs with the message Guest has not initialized the display yet. Instead of extracting VMWare's bios.rom, I used UEFITool on OVMF.fd to the same end. This trick doesn't seem to work anymore as detailed in this issue. ![]() I have followed the vmware-vmx.exe injection guide suggested in the previous link. GoalĬreate a development environment to test that my DXE drivers are being properly injected into an UEFI firmware image. This is an attempt to follow the first bullet point in this answer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |