Hi Richard,
> Platform: riscv64-unknown-linux-gnu
> gnulib @ db0b059ae4f489d0c83b785b259eb965a181d0d0 (yesterday)
Prompted by your mail, I'm trying to run a Linux/riscv64 machine in a qemu
VM, in order to look at the gnulib problems and port GNU libffcall and other
software. According to [1], I'm using qemu built from upstream qemu today with
options
--target-list=riscv32-softmmu,riscv64-softmmu,riscv32-linux-user,riscv64-linux-user
According to [2], I'm taking your disk image and running it as
qemu-system-riscv64 \
-nographic -machine virt -m 2G -smp 4 \
-kernel bbl \
-append "console=ttyS0 ro root=/dev/vda init=/init" \
-device virtio-blk-device,drive=hd0 \
-drive file=stage4-disk.img,format=raw,id=hd0 \
-device virtio-net-device,netdev=usernet \
-netdev user,id=usernet
and it fails like this:
EXT4-fs (vda): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (vda): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (vda): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 254:0.
Freeing unused kernel memory: 200K
This architecture does not have kernel memory protection.
Kernel panic - not syncing: Requested init /init failed (error -2).
CPU: 1 PID: 1 Comm: swapper/3 Tainted: G W
4.16.0-rc2-00328-gebea62367bc4 #4
Call Trace:
[<ffffffe0000341ee>] walk_stackframe+0x0/0xa2
[<ffffffe0000342ec>] show_stack+0x26/0x34
[<ffffffe0005e4904>] dump_stack+0x5e/0x7c
[<ffffffe00003771a>] panic+0xce/0x1e8
[<ffffffe0005f5430>] kernel_init+0x94/0xf0
[<ffffffe000033242>] ret_from_syscall+0xa/0xe
The message "This architecture does not have kernel memory protection." seems
to indicate some differences between the qemu you are using and the official
upstream one. Can you help, please?
Bruno
[1] https://wiki.debian.org/RISC-V
[2]
https://netcreator.us/news/10245-richard-w-m-jones-fedora-risc-v-runnable-stage-4-disk-images.html
