From: pintu.ping@gmail.com (Pintu Kumar)
To: linux-riscv@lists.infradead.org
Subject: riscv-qemu - linux boot is failing for vda device
Date: Mon, 15 Oct 2018 19:30:59 +0530 [thread overview]
Message-ID: <CAOuPNLgimMwWrw6oXs7Eu8xBG+geOt53D_LjiiNk7=OEtLtz3g@mail.gmail.com> (raw)
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
But, I am getting kernel panic.
---------
bbl loader
....
Linux version 4.18.0-rc6...
....
devtmpfs: initialized
cpu cpu0: Error -2 creating of_node link
......
SCSI subsystem initialized
....
Unpacking initramfs...
....
loop: module loaded
virtio_blk: probe of virtio0 failed with error -22
...
VFS: Cannot open root device "vda" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-rc6-13927-gd72e90f3 #3
-----------
Basically, it could not find the "vda" device, even though I passed
the "root=/dev/vda"
What could be the cause of this issue?
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_VIRTIO_BLK=y
# CONFIG_VIRTIO_BLK_SCSI is not set
# CONFIG_SCSI_VIRTIO is not set
CONFIG_VIRTIO_NET=y
These are already enabled in the kernel.
If I am missing any config, please let me know.
Thanks,
Pintu
WARNING: multiple messages have this Message-ID (diff)
From: Pintu Kumar <pintu.ping@gmail.com>
To: isa-dev@groups.riscv.org, linux-riscv@lists.infradead.org
Subject: riscv-qemu - linux boot is failing for vda device
Date: Mon, 15 Oct 2018 19:30:59 +0530 [thread overview]
Message-ID: <CAOuPNLgimMwWrw6oXs7Eu8xBG+geOt53D_LjiiNk7=OEtLtz3g@mail.gmail.com> (raw)
Message-ID: <20181015140059.wVi7QCH1kqNFV0zExnHYmnOSpBLXhkesquFm8P12kcI@z> (raw)
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
But, I am getting kernel panic.
---------
bbl loader
....
Linux version 4.18.0-rc6...
....
devtmpfs: initialized
cpu cpu0: Error -2 creating of_node link
......
SCSI subsystem initialized
....
Unpacking initramfs...
....
loop: module loaded
virtio_blk: probe of virtio0 failed with error -22
...
VFS: Cannot open root device "vda" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-rc6-13927-gd72e90f3 #3
-----------
Basically, it could not find the "vda" device, even though I passed
the "root=/dev/vda"
What could be the cause of this issue?
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_VIRTIO_BLK=y
# CONFIG_VIRTIO_BLK_SCSI is not set
# CONFIG_SCSI_VIRTIO is not set
CONFIG_VIRTIO_NET=y
These are already enabled in the kernel.
If I am missing any config, please let me know.
Thanks,
Pintu
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-10-15 14:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 14:00 Pintu Kumar [this message]
2018-10-15 14:00 ` riscv-qemu - linux boot is failing for vda device Pintu Kumar
2018-10-15 20:26 ` [isa-dev] " Michael Clark
2018-10-15 20:26 ` Michael Clark
2018-10-15 21:14 ` [sw-dev] " Richard W.M. Jones
2018-10-15 21:14 ` 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='CAOuPNLgimMwWrw6oXs7Eu8xBG+geOt53D_LjiiNk7=OEtLtz3g@mail.gmail.com' \
--to=pintu.ping@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).