Greetings,
I'm trying to test a new initramfs I'm working on for a system I have, I don't want to test on a live system to I'm trying to get qemu to work.
I've created a dummy fs to boot after, grabbed a kernel and skeleton initramfs, I ran this cmd: qemu-system-x86_64 -bios /usr/share/edk2/OvmfX64/OVMF_CODE.fd -kernel vmlinuz-linux-6.14.2-gentoo -nographic -append "console=ttyS0" -initrd initramfs -drive format=raw,file=guest.img.raw
and I get efi shell, what am I doing wrong?
booting custom kernel and initrd in qemu unde efi [aolved]
Message
- DaggyStyle
- Watchman
- Posts: 5969
- Joined: Wed Mar 22, 2006 6:57 am
booting custom kernel and initrd in qemu unde efi [aolved]
Last edited by DaggyStyle on Sun Apr 13, 2025 5:29 pm, edited 1 time in total.
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
- DaggyStyle
- Watchman
- Posts: 5969
- Joined: Wed Mar 22, 2006 6:57 am
Do you even need UEFI for initramfs test? if not just take out "-bios /usr/share/edk2/OvmfX64/OVMF_CODE.fd" from your qemu command.
UEFI is a pre-boot management services (or specification if you insist) and your qemu command already specific kernel file location, so there is no need to invoke UEFI.
UEFI is a pre-boot management services (or specification if you insist) and your qemu command already specific kernel file location, so there is no need to invoke UEFI.
- DaggyStyle
- Watchman
- Posts: 5969
- Joined: Wed Mar 22, 2006 6:57 am
(facepalm) you are correct, I'm missing to much sleep hours.pingtoo wrote:Do you even need UEFI for initramfs test? if not just take out "-bios /usr/share/edk2/OvmfX64/OVMF_CODE.fd" from your qemu command.
UEFI is a pre-boot management services (or specification if you insist) and your qemu command already specific kernel file location, so there is no need to invoke UEFI.
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein