qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Dominique Martinet <dominique.martinet@cea.fr>
Cc: Richard Yao <ryao@gentoo.org>,
	qemu-devel@nongnu.org, agraf@suse.de, kernel@gentoo.org,
	v9fs-developer@lists.sourceforge.net,
	virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [V9fs-developer] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
Date: Fri, 22 Aug 2014 13:54:14 -0400	[thread overview]
Message-ID: <53F783C6.2030409@codeaurora.org> (raw)
In-Reply-To: <20140822124906.GA13229@u-galfione>

Hi Dominique,

On 08/22/2014 08:49 AM, Dominique Martinet wrote:
> Hi,
> 
> Christopher Covington wrote on Fri, Aug 22, 2014 at 08:37:52AM -0400:
>> Thanks for the pointer to this patch. I think I started this kernel half way
>> through the 3.16 merge window. The last non-cherry-picked patch I have is:
>>
>> commit 6d87c225f5d82d29243dc124f1ffcbb0e14ec358
>>
>> So I do have the change you pointed out. Nevertheless, I'll reconfirm with the
>> latest torvalds/master.
> 
> Right, so you already do have it. I don't think there's been anything
> else 9P related recently, so it probably will not help much -- sorry for
> blindly assuming it would be this.
> 
> Actually reading the error message now, "no channels available" is
> printed when virtio doesn't find any match in device name so it would
> look like the mount name doesn't match maybe?
> 
> Could we get your exact qemu command line to confirm? (the name that
> needs to match is /dev/root here, used for booting as root= and for qemu
> as mount_tag)

I re-transposed Richard's command line to my environment and it worked. Thanks
for pointing me in that direction. For the record, I used:

$dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \
  -m 1024 \
  -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \
  -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p
rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \
  -serial stdio \
  -fsdev local,id=root,path=$dir,security_model=none \
  -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \
  -monitor none

$dir/bin/x86_64-linux-gnu/qemu-system-arm \
  -M virt \
  -cpu cortex-a15 \
  -m 1024 \
  -kernel $dir/boot/arm-linux-gnueabihf/Image \
  -append 'root=/dev/root init=/sbin/arm-linux-gnueabihf/init rootfstype=9p
rootflags=trans=virtio,version=9p2000.L ro console=ttyAMA0' \
  -serial stdio \
  -fsdev local,id=root,path=$dir,security_model=none \
  -device virtio-9p-device,fsdev=root,mount_tag=/dev/root \
  -monitor none

$dir/bin/x86_64-linux-gnu/qemu-system-aarch64 \
  -M virt \
  -cpu cortex-a57 \
  -m 1024 \
  -kernel $dir/boot/aarch64-linux-gnu/Image \
  -append 'root=/dev/root init=/sbin/aarch64-linux-gnu/init rootfstype=9p
rootflags=trans=virtio,version=9p2000.L ro console=ttyAMA0' \
  -serial stdio \
  -fsdev local,id=root,path=$dir,security_model=none \
  -device virtio-9p-device,fsdev=root,mount_tag=/dev/root -monitor none

Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

      reply	other threads:[~2014-08-22 17:54 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
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 [this message]

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=53F783C6.2030409@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=agraf@suse.de \
    --cc=dominique.martinet@cea.fr \
    --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).