Re: RISC-V virtual machine does not boot anymore
On Sun, Mar 22, 2020 at 04:41:16PM +0100, Giovanni Mascellani wrote:
> Il 12/12/19 14:44, Giovanni Mascellani ha scritto:
> > Hi!
> >
> > 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:
>
> For the record, this was solved (I believe by Vagrant's patches), but
> has reappeared again. Or maybe something else similar. Everything is the
> same as my previous report except the last few lines which are now:
>
> > U-Boot menu
> > 1: Debian GNU/Linux kernel 5.4.0-4-riscv64
> > 2: Debian GNU/Linux kernel 5.4.0-4-riscv64 (rescue target)
> > Enter choice: 1
> > 1: Debian GNU/Linux kernel 5.4.0-4-riscv64
> > Retrieving file: /boot/initrd.img-5.4.0-4-riscv64
> > 50611442 bytes read in 10 ms (4.7 GiB/s)
> > Retrieving file: /boot/vmlinux-5.4.0-4-riscv64
> > 9389848 bytes read in 2 ms (4.4 GiB/s)
> > append: rw noquiet root=/dev/vda1
> > exception code: 5 , Load access fault , epc f9943f54 , ra f99046a8
> > ### ERROR ### Please RESET the board ###
>
> Thanks again to those having magic powers which can solve this.
Hello,
removing the fdtdir parameter in the U-Boot config so that
U-Boot passes its internal DT instead of trying to load an
external DT from the filesystem makes it work, cf.
https://lists.debian.org/debian-riscv/2019/12/msg00003.html.
I have updated the description of how to setup a RISC-V virtual
machine in the Debian wiki accordingly.
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: