From: Christopher Covington <cov@codeaurora.org>
To: Richard Yao <ryao@gentoo.org>
Cc: kernel@gentoo.org, v9fs-developer@lists.sourceforge.net,
virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
agraf@suse.de
Subject: Re: [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
Date: Thu, 21 Aug 2014 15:50:58 -0400 [thread overview]
Message-ID: <53F64DA2.3060308@codeaurora.org> (raw)
In-Reply-To: <5293718E.4090508@gentoo.org>
Hi Richard,
On 11/25/2013 10:49 AM, Richard Yao wrote:
> I booted a Gentoo Linux installation in QEMU with a 9P rootfs as follows:
>
> sudo qemu-kvm -cpu host -m 1024 -kernel
> /mnt/test/usr/src/linux-3.13-rc1/arch/x86/boot/bzImage -append
> 'root=/dev/root rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro
> console=ttyS0' -serial stdio -fsdev
> local,id=root,path=/mnt/test,security_model=none -device
> virtio-9p-pci,fsdev=root,mount_tag=/dev/root
>
> The system boots fine, but attempting to load any module will fail:
>
> localhost ~ # modprobe crc32
> qemu-system-x86_64: virtio: trying to map MMIO memory
>
> The behavior is consistent no matter what combination of things that I
> try. So far, I have tried Linux 3.10.7-gentoo (Gentoo patchset) and
> Linux 3.13-rc1. I have tried QEMU 1.4.2, QEMU 1.6.1 and QEMU HEAD. I
> have also tried booting without KVM, but the behavior is the same:
>
> sudo qemu-kvm --no-kvm -m 1024 -kernel
> /mnt/test/usr/src/linux-3.13-rc1/arch/x86/boot/bzImage -append
> 'root=/dev/root rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro
> console=ttyS0' -serial stdio -fsdev
> local,id=root,path=/mnt/test,security_model=none -device
> virtio-9p-pci,fsdev=root,mount_tag=/dev/root
Have you used this setup recently?
With my 3.15.0+ kernel, qemu-system-x86_64 substituted for qemu-kvm, and the
path changed from your arguments I get:
9pnet_virtio: no channels available
VFS: Cannot open root device "root" or unknown-block(0,0): error -2
Please append a correct "root=" boot option; here are the available partitions:
0b00 1048575 sr0 driver: sr
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-08-21 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 15:49 [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs Richard Yao
2013-11-25 21:50 ` Richard Yao
2013-11-26 15:16 ` Christopher Covington
2013-11-26 15:38 ` Richard Yao
2013-11-26 15:47 ` Richard Yao
2014-08-21 19:50 ` Christopher Covington [this message]
2014-08-22 3:00 ` Richard Yao
2014-08-22 6:27 ` [Qemu-devel] [V9fs-developer] " Dominique Martinet
2014-08-22 12:37 ` Christopher Covington
2014-08-22 12:49 ` Dominique Martinet
2014-08-22 17:54 ` Christopher Covington
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=53F64DA2.3060308@codeaurora.org \
--to=cov@codeaurora.org \
--cc=agraf@suse.de \
--cc=kernel@gentoo.org \
--cc=qemu-devel@nongnu.org \
--cc=ryao@gentoo.org \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.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).