riscv-software-src / riscv-software-src/opensbi
qemu-system-riscv64: -append only allowed with -kernel option
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 712
- PR merge metrics
- No merged PRs in 30d
Description
I was trying to pass the Linux Kernel as a payload to OpenSBI to launch Qemu-Virt, and I found that the instructions in opensbi/docs/platform/qemu_virt.md might be problematic:
qemu-system-riscv64 -M virt -m 256M -nographic \
-bios build/platform/generic/firmware/fw_payload.elf \
-drive file=<path_to_linux_rootfs>,format=raw,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-append "root=/dev/vda rw console=ttyS0"
However, in the Qemu version I use (Qemu-7.2.0), it will prompt: qemu-system-riscv64: -append only allowed with -kernel option, so the above method of passing bootargs to the kernel may not be feasible.
Contributor guide
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
Read opensbi/docs/platform/qemu_virt.md and reproduce the documented command with Qemu-7.2.0. Check how boot arguments should be passed when -append requires -kernel, then update the instructions so the Qemu-Virt Linux launch procedure works and remains clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100