rust-osdev / rust-osdev/bootloader
Boot prcess gets sometimes stuck at "TRACE: exiting boot services" when using Uefi and qemu
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Description
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)
- ovmf-prebuilt = "0.1.0-alpha.1"
- occurred independent of used BootloaderConfig
- never encountered on hardware
- occurred on Linux, Mac and Windows hosts
- my toy Os repo: https://github.com/daniel-keitel/Steelmind_OS
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the provided qemu-system-x86_64 command and the boot log, varying the -smp core count. Start from the UEFI boot path around “TRACE: exiting boot services” and compare behavior across core counts and the listed host platforms. Done means identifying why the bootloader can remain stuck under QEMU and documenting or fixing that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100