Risc-V, qemu, and initrd

From: linux@roeck-us.net (Guenter Roeck)
To: linux-riscv@lists.infradead.org
Subject: Risc-V, qemu, and initrd
Date: Fri, 22 Jun 2018 09:34:07 -0700	[thread overview]
Message-ID: <20180622163407.GA13770@roeck-us.net> (raw)
In-Reply-To: <20180622053805.GA19304@infradead.org>

On Thu, Jun 21, 2018 at 10:38:05PM -0700, Christoph Hellwig wrote:
> On Thu, Jun 21, 2018 at 03:08:59PM -0700, Guenter Roeck wrote:
> > On Thu, Jun 21, 2018 at 10:55:09AM -0700, Christoph Hellwig wrote:
> > > On Thu, Jun 21, 2018 at 10:33:14AM -0700, Guenter Roeck wrote:
> > > > Are you able to boot anything but -M virt ? If yes, can you send me the
> > > > necessary command line parameters ?
> > > 
> > > Just -m virt.  For the SiFive board emulations a lot more driver
> > > support is required.
> > 
> > Ok. At least it is a start. Have you managed to connect a hard drive ?
> > I was only able to get it to work with initrd.
> 
> Yes, I use virtio-blk.  Here is my qemu command line:
> 
> /opt/qemu-riscv/bin/qemu-system-riscv64 \
>         -nographic \
>         -machine virt \
>         -kernel bbl \
>         -append "root=/dev/vda ro console=ttyS0" \
>         -drive file=../../busybear-linux/busybear.bin,format=raw,id=hd0 \
>         -device virtio-blk-device,drive=hd0 \
>         -netdev user,id=net0, \
>         -device virtio-net-device,netdev=net0
> 

Yes, that worked. For some reason I had tried to use virtio-scsi-device.

With your Linux kernel ToT, after removing setup_initrd(), and with qemu
built from riscv/qemu-2.13-for-upstream, my testing now reports:

Building virt:defconfig:initrd ... running .... passed
Building virt:defconfig:rootfs ... running .... passed

Let's hope that upstream Linux soon gets to a point where I can activate
those tests.

Thanks a lot!

Guenter