Re: RISC-V virtual machine does not boot anymore
On Thu, Dec 12, 2019 at 02:44:01PM +0100, Giovanni Mascellani wrote:
> The instructions for creating a RISC-V virtual machine do not work
> anymore for me (on an updated amd64 unstable machine). I follow
> precisely the instructions at [1] and everything seems fine (no strange
> error message), except that actually running the machine does not work:
>
> > $ qemu-system-riscv64 -nographic -machine virt -m 1.9G \
> >> -kernel /usr/lib/riscv64-linux-gnu/opensbi/qemu/virt/fw_jump.elf \
> >> -device loader,file=/usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin,addr=0x80200000 \
> >> -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 \
> >> -append "console=ttyS0 rw root=/dev/vda1" \
> >> -device virtio-blk-device,drive=hd0 -drive file=rootfs.img,format=raw,id=hd0 \
> >> -device virtio-net-device,netdev=usernet -netdev user,id=usernet,hostfwd=tcp::22222-:22
> > qemu-system-riscv64: warning: No -bios option specified. Not loading a firmware.
> > qemu-system-riscv64: warning: This default will change in a future QEMU release. Please use the -bios option to avoid breakages when this happens.
> > qemu-system-riscv64: warning: See QEMU's deprecation documentation for details.
> >
> > OpenSBI v0.5 (Oct 12 2019 06:02:51)
> > ____ _____ ____ _____
> > / __ \ / ____| _ \_ _|
> > | | | |_ __ ___ _ __ | (___ | |_) || |
> > | | | | '_ \ / _ \ '_ \ \___ \| _ < | |
> > | |__| | |_) | __/ | | |____) | |_) || |_
> > \____/| .__/ \___|_| |_|_____/|____/_____|
> > | |
> > |_|
> >
> > Platform Name : QEMU Virt Machine
> > Platform HART Features : RV64ACDFIMSU
> > Platform Max HARTs : 8
> > Current Hart : 0
> > Firmware Base : 0x80000000
> > Firmware Size : 116 KB
> > Runtime SBI Version : 0.2
> >
> > PMP0: 0x0000000080000000-0x000000008001ffff (A)
> > PMP1: 0x0000000000000000-0xffffffffffffffff (A,R,W,X)
> >
> >
> > U-Boot 2019.10+dfsg-1 (Oct 17 2019 - 19:23:42 +0000)
> >
> > CPU: rv64imafdcsu
> > Model: riscv-virtio,qemu
> > DRAM: 1.9 GiB
> > In: uart@10000000
> > Out: uart@10000000
> > Err: uart@10000000
> > Net:
> > Warning: virtio-net#2 using MAC address from ROM
> > eth0: virtio-net#2
> > Hit any key to stop autoboot: 0
> >
> > Device 0: QEMU VirtIO Block Device
> > Type: Hard Disk
> > Capacity: 10240.0 MB = 10.0 GB (20971520 x 512)
> > ... is now current device
> > Scanning virtio 0:1...
> > Found /boot/extlinux/extlinux.conf
> > Retrieving file: /boot/extlinux/extlinux.conf
> > 699 bytes read in 3 ms (227.5 KiB/s)
> > U-Boot menu
> > 1: Debian GNU/Linux kernel 5.3.0-3-riscv64
> > 2: Debian GNU/Linux kernel 5.3.0-3-riscv64 (rescue target)
> > Enter choice: 1: Debian GNU/Linux kernel 5.3.0-3-riscv64
> > Retrieving file: /boot/initrd.img-5.3.0-3-riscv64
> > 49162351 bytes read in 10 ms (4.6 GiB/s)
> > Retrieving file: /boot/vmlinux-5.3.0-3-riscv64
> > 9217544 bytes read in 4 ms (2.1 GiB/s)
> > append: rw noquiet root=/dev/vda1
> > exception code: 5 , Load access fault , epc f994443e , ra f990577e
> > ### ERROR ### Please RESET the board ###
>
> [1] https://wiki.debian.org/RISC-V#Creating_a_riscv64_chroot
>
> QEMU remains blocked there until I kill it. I have no idea which
> component broke. The same procedure used to work in the past.
Hello,
the breakage happens with the move from kernel 5.2 to 5.3;
everything works fine with kernel package 5.2.0-3-riscv64 but
doesn't work anymore with 5.3.0-1-riscv64 and newer.
I had tried to narrow down the problem further but haven't been
successfull and unfortunately I currently lack the time for
further debugging, so if somebody else could take a look that
would be great.
Regards,
Karsten
--
Ich widerspreche hiermit ausdrücklich der Nutzung sowie der
Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung
sowie der Markt- oder Meinungsforschung.
Reply to: