-
Notifications
You must be signed in to change notification settings - Fork 56
Failed to run Ubuntu/Debian on QEMU RISC-V #29
Comments
Hey! Have you figure it out? I have the exact same problem as well. That is my console log:
So I think the problem might be the |
I'm not sure if this is a right approach, but I succeeded in booting it up by creating root filesystem image from
https://github.com/takahirox/riscv-rust/tree/master/resources/linux/opensbi |
@takahirox Thank you for you approach. It works! The only problem I had was with busybox 1_32_0. I got the following error when I used 1_32_0 or 1_32_stable or 1_31_0.
OS Ubuntu 20.10. The workaround is to checkout busybox version 1_30_stable. |
I was able to run RISC-V Debian GNU/Linux bullseye/sid via QEMU.
QEMU VM loading output:
|
Hey @takahirox thanks for the setups, it solved my issue for rootfs but am popped with issue of initfs, any idea how to solve this (ik thread is old :( but hoping for the input). Below are all the logs :
|
You need to compile busybox staticlly. try "make menuconfig" and set "Settings/Build static binary(no shared libs)" |
Hi @rushi47 , It might be a little late to reply. When you boot into linux, your kernel searches for an init file to mount necessary devices. Typically it is in
Also it will be a better approach to compress the generated busybox file system in |
I followed the instructions in RISC-V getting started guide with #26 and #28 to run Ubuntu/Debian on QEMU RISC-V. But failed to do that.
After building QEMU, Linux, Busybox, I ran the following command to boot QEMU RISC-V with Ubuntu.
https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html#running
But I faced the following warnings and see no other messages.
I also tried
-bios default
option but it seems to fail to mount root fs.Do I need to pass a certain bios file to QEMU? Or am I missing something? Does anyone succeeded in booting Ubuntu/Debian on QEMU RISC-V with the guideline?
The text was updated successfully, but these errors were encountered: