From: rjones@redhat.com (Richard W.M. Jones)
To: linux-riscv@lists.infradead.org
Subject: [sw-dev] Re: [isa-dev] riscv-qemu - linux boot is failing for vda device
Date: Mon, 15 Oct 2018 22:14:51 +0100 [thread overview]
Message-ID: <20181015211451.GC31130@redhat.com> (raw)
In-Reply-To: <0D61A5C7-23B7-466E-BE00-458675DE4FF7@mac.com>
On Tue, Oct 16, 2018 at 09:26:20AM +1300, 'Michael Clark' via RISC-V SW Dev wrote:
> Dropping isa-dev, adding sw-dev
>
> > On 16/10/2018, at 3:00 AM, Pintu Kumar <pintu.ping@gmail.com> wrote:
> >
> > Hi,
> > I am trying to setup riscv-qemu booting on a new Ubuntu PC.
> > I dont want to use freedom-u-sdk, so I am preparing my own environment.
> > I could able to build the following:
> > - riscv-toolchain
> > - riscv-linux
> > - riscv-qemu
> > - riscv-pk
> > - busybear
> >
> > After that, I am trying to boot riscv-qemu, using the following command:
> > # sudo qemu-system-riscv64 -nographic -machine virt -kernel
> > PK/riscv-pk/build/bbl -append "root=/dev/vda ro console=ttyS0" -drive
> > file=busybear.bin,format=raw,id=hd0 -device
> > virtio-blk-device,drive=hd0
>
> Note: sudo is not required. sudo is used in the busybear start-qemu.sh script as it uses bridged networking. The latest version of busybear points at linux-4.19-rc5 so the issue may have been fixed.
>
> > But, I am getting kernel panic.
> >
> > ---------
> > bbl loader
> > ....
> > Linux version 4.18.0-rc6...
It's a bit of a guess, but could this be the upstream kernel? The
latest riscv-linux is 4.18.0 (not -rc6).
The reason I say it might be the upstream kernel is because ...
> > virtio_blk: probe of virtio0 failed with error -22
... I saw this exact error when I was using the upstream kernel
instead of the one which supported interrupt handling. Interrupt
handling for RISC-V was added upstream after 4.18 so wouldn't be
included in upstream 4.18.0-rc6.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
WARNING: multiple messages have this Message-ID (diff)
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Michael Clark <michaeljclark@mac.com>
Cc: linux-riscv@lists.infradead.org, sw-dev@groups.riscv.org,
Pintu Kumar <pintu.ping@gmail.com>
Subject: Re: [sw-dev] Re: [isa-dev] riscv-qemu - linux boot is failing for vda device
Date: Mon, 15 Oct 2018 22:14:51 +0100 [thread overview]
Message-ID: <20181015211451.GC31130@redhat.com> (raw)
Message-ID: <20181015211451.TJrng6s8i2g5zKkIS9FhzB9V_Eiyc66lBigTCdPlNvU@z> (raw)
In-Reply-To: <0D61A5C7-23B7-466E-BE00-458675DE4FF7@mac.com>
On Tue, Oct 16, 2018 at 09:26:20AM +1300, 'Michael Clark' via RISC-V SW Dev wrote:
> Dropping isa-dev, adding sw-dev
>
> > On 16/10/2018, at 3:00 AM, Pintu Kumar <pintu.ping@gmail.com> wrote:
> >
> > Hi,
> > I am trying to setup riscv-qemu booting on a new Ubuntu PC.
> > I dont want to use freedom-u-sdk, so I am preparing my own environment.
> > I could able to build the following:
> > - riscv-toolchain
> > - riscv-linux
> > - riscv-qemu
> > - riscv-pk
> > - busybear
> >
> > After that, I am trying to boot riscv-qemu, using the following command:
> > # sudo qemu-system-riscv64 -nographic -machine virt -kernel
> > PK/riscv-pk/build/bbl -append "root=/dev/vda ro console=ttyS0" -drive
> > file=busybear.bin,format=raw,id=hd0 -device
> > virtio-blk-device,drive=hd0
>
> Note: sudo is not required. sudo is used in the busybear start-qemu.sh script as it uses bridged networking. The latest version of busybear points at linux-4.19-rc5 so the issue may have been fixed.
>
> > But, I am getting kernel panic.
> >
> > ---------
> > bbl loader
> > ....
> > Linux version 4.18.0-rc6...
It's a bit of a guess, but could this be the upstream kernel? The
latest riscv-linux is 4.18.0 (not -rc6).
The reason I say it might be the upstream kernel is because ...
> > virtio_blk: probe of virtio0 failed with error -22
... I saw this exact error when I was using the upstream kernel
instead of the one which supported interrupt handling. Interrupt
handling for RISC-V was added upstream after 4.18 so wouldn't be
included in upstream 4.18.0-rc6.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-10-15 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 14:00 riscv-qemu - linux boot is failing for vda device Pintu Kumar
2018-10-15 14:00 ` Pintu Kumar
2018-10-15 20:26 ` [isa-dev] " Michael Clark
2018-10-15 20:26 ` Michael Clark
2018-10-15 21:14 ` Richard W.M. Jones [this message]
2018-10-15 21:14 ` [sw-dev] " Richard W.M. Jones
2018-10-16 0:40 ` Palmer Dabbelt
2018-10-16 0:40 ` Palmer Dabbelt
2018-10-16 13:12 ` Pintu Kumar
2018-10-16 13:12 ` Pintu Kumar
2018-10-16 13:30 ` Richard W.M. Jones
2018-10-16 13:30 ` Richard W.M. Jones
2018-10-16 18:38 ` Palmer Dabbelt
2018-10-16 18:38 ` Palmer Dabbelt
2018-10-16 20:02 ` Karsten Merker
2018-10-16 22:30 ` Michael Clark
2018-10-16 22:30 ` Michael Clark
2018-10-17 5:19 ` Karsten Merker
2018-10-17 7:34 ` Michael Clark
2018-10-17 7:34 ` Michael Clark
2018-10-17 12:03 ` Pintu Agarwal
2018-10-17 12:03 ` Pintu Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181015211451.GC31130@redhat.com \
--to=rjones@redhat.com \
--cc=linux-riscv@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.