bootloader icon indicating copy to clipboard operation
bootloader copied to clipboard

Published 20 hours ago • verified publisher icon rust-osdev

Bootloader not working with -device q35

Open Andy-Python-Programmer opened this issue 4 years ago • 4 comments

Bootloader does not work with -device q35 argument passed to qemu to access the MCFG tables and SATA. Heres the output:

image

[dependencies.bootloader]
version = "0.9.16"
features = ["map_physical_memory"]

Andy-Python-Programmer avatar Mar 28 '21 00:03 Andy-Python-Programmer

Hmm, I never tried to use q35. Looks like it doesn't even detect the boot disk. Could you try whether it works with other system images? This would tell us whether the problem is in the disk image generated by this crate or whether it is in QEMU itself.

phil-opp avatar Mar 28 '21 09:03 phil-opp

Hmm, I never tried to use q35. Looks like it doesn't even detect the boot disk. Could you try whether it works with other system images? This would tell us whether the problem is in the disk image generated by this crate or whether it is in QEMU itself.

I did try it with another image before I tried it with this crate and it seems to work. This crate seems to be the err. @phil-opp

Andy-Python-Programmer avatar Mar 28 '21 09:03 Andy-Python-Programmer

Thanks for the quick reply! I suspect that is because we currently only write the boot signature 0x55aa, but not any partition table. I'll try to fix this soon, but I'm currently still busy with the rewrite for UEFI support.

phil-opp avatar Mar 28 '21 10:03 phil-opp

We now create a proper FAT partition for booting. Does this issue still occur with v0.11?

phil-opp avatar Jan 02 '23 12:01 phil-opp