You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running qemu-system-x86_64 -bios {ovmf_pure_efi_path} -drive format=raw,file={uefi_path} -smp {core_count}
the bootloader gets sometimes stuck at:
INFO : UEFI bootloader started
INFO : Using framebuffer at 0xc0000000
INFO : Reading configuration from disk was successful
INFO : Trying to load ramdisk via Disk
INFO : Ramdisk not found.
TRACE: exiting boot services
Higher core counts for the -smp argument result in a higher likelihood of it getting stuck.
(I am not sure if it even occurred once at -smp 1)
I have the same issue, so I don't think it is related to either the kernel or the configuration.
Also I tried running this repos tests using smp and got the same error.
I'll spend some time investigating this. This bug is rather annoying when trying to run automated tests.
Wasabi375
added a commit
to Wasabi375/bootloader
that referenced
this issue
Sep 17, 2024
Switch from using the "-bios" flag to using "-pflash" instead.
Using "-bios" is not recomended see:
https://lists.katacontainers.io/pipermail/kata-dev/2021-January/001650.html
This also allows us to easily update the ovmf-prebuild binaries.
This fixesrust-osdev#400. I'm not sure whether the issue was an outdated ovmf
version or the bios-pflash change. I can't tell what version is
published with the ovmf-prebuild crate, so I can't check.
Ovmf binaries are no longer provided by the ovmf-prebuild crate.
Instead we now download them from the ovmf-prebuild github releases of
the same crate. Unlike the crate, those are actually updated.
Fixesrust-osdev#400
When running
qemu-system-x86_64 -bios {ovmf_pure_efi_path} -drive format=raw,file={uefi_path} -smp {core_count}
the bootloader gets sometimes stuck at:
Higher core counts for the -smp argument result in a higher likelihood of it getting stuck.
(I am not sure if it even occurred once at -smp 1)
The text was updated successfully, but these errors were encountered: