-
Notifications
You must be signed in to change notification settings - Fork 29
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
gok vm --arch arm64: sometimes throws Synchronous Exception #80
Comments
Could it be due to a version discrepancy between the qemu version I'm running Is this related https://gitlab.archlinux.org/archlinux/packaging/packages/edk2/-/issues/4 ? |
Found this in the QEMU 9.0 release notes (source):
And I have a hunch this might be what's causing issue, considering it is a pulsing one, the theory that it is triggered by a bug migth explain this. Should we update the QEMU_EFI to be after 202311 ? Will this force a minumum the version of QEMU? |
Generally, UEFI should be compatible in both directions, but apparently not always :D Yeah, upgrading to a (probably very recent) edk2 seems fine to me. Do you want to give it a try and see if it solves the problem for you? |
it updates the arm64 UEFI firmware to a version newer than 2023.11, as running on qemu >= 9.0 can trigger a bug in the older versions of the EDK2 guest firmware, causing Synchronous Exception and potential bootloops. While doing so it updates the amd64 OVMF firmware, which now has removed support for the 2M firmware and only supports the 4M one. The 4M OVMF firmware comes with split CODE and VARS images, which need to be loaded as pflash drives in the qemu vm, rather than via the -bios flag. For more details on the migration see: https://salsa.debian.org/qemu-team/edk2/-/blob/debian/latest/debian/howto-2M-to-4M-migration.md Fixes gokrazy#80
Yeah, that would make sense, it sounds like they didn't meant to break that. Anyway here is the PR to bump things: #81 Please let me know if it works for older versions of qemu if you are running one (e.g. 7.y or 8.y) Thanks! |
it updates the arm64 UEFI firmware to a version newer than 2023.11, as running on qemu >= 9.0 can trigger a bug in the older versions of the EDK2 guest firmware, causing Synchronous Exception and potential bootloops. While doing so it updates the amd64 OVMF firmware, which now has removed support for the 2M firmware and only supports the 4M one. The 4M OVMF firmware comes with split CODE and VARS images, which need to be loaded as pflash drives in the qemu vm, rather than via the -bios flag. For more details on the migration see: https://salsa.debian.org/qemu-team/edk2/-/blob/debian/latest/debian/howto-2M-to-4M-migration.md Fixes gokrazy#80
OS
darwin / macOS Sonoma 14.7.2
Arch:
Apple M3 Pro (arm64)
gok
qemu
Sometimes, like ~50% of the times the following command
yields this exception:
This is my current
config.json
:Edit: 1
This issue only happens when running arm64 vms, so with
gok vm --arch arm64
and it doesn't withgok vm --arch amd64
(with of course a changed config.json and the correct kernel and env var flags).The text was updated successfully, but these errors were encountered: