-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UEFI boot #471
Comments
P.S. If you have a valid UEFI bootable HDD on |
I noticed problems with disk emulation in Bochs in the past as well. |
I think this is an error in OVMF, not Bochs. OVMF sends the I made a little test to return 0xFF on all reads from ata1 (0x170 -> 0x177) except for 0x177 which returns 0x00 and the OVMF booted as expected when ATA1 is disabled. I did not look at the second issue I noted.
|
There might be something wrong with the UEFI emulation.
Here is a test situation.
Get the latest UEFI from https://www.kraxel.org/repos/jenkins/edk2/.
I use
OVMF-pure-efi.fd
from the x64 version. Also extractUefiSheel.iso
from that same rpmNow try to boot the ISO. Here is a demo
bochrc.txt
file. Note thatata1:
is disabled...It hangs. However, if you make the following change:
It boots to the Shell as expected.
Go back to the hang and look at the serial out:
It can't open the file.
I can confirm that it finds, loads, and boots fine from an HDD image.
Since this is the case, and QEMU (using the same efi image) finds and loads the ISO image, there must be something different with Bochs' ATA emulation when UEFI is loaded.
.
.
.
On a side note, the emulation also has the following complaint.
Using the
OVMF_CODE-need-smm.fd
file does not have the same complaint.The text was updated successfully, but these errors were encountered: