All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rlandley@parallels.com>
To: qemu-devel@nongnu.org, Eric Van Hensbergen <ericvh@gmail.com>
Subject: [Qemu-devel] virtfs error reporting?
Date: Sun, 24 Apr 2011 14:31:38 -0500	[thread overview]
Message-ID: <4DB47A9A.5050504@parallels.com> (raw)

So on the host side I'm trying to do this:

$ qemu -cpu pentium3 -nographic -no-reboot -kernel bzImage \
  -hda hda.sqf -append 'root=/dev/hda rw init=/sbin/init.sh panic=1 \
  PATH=/bin:/sbin console=ttyS0 HOST=i686 ' -net nic,model=e1000 \
  -net user -virtfs local,path=../root-filesystem-i686,security_model=mapped,mount_tag=root

And on the guest side I'm trying to do this:

  mount -t 9p -o ro,trans=virtio,version=9p2000.L root /mnt

And it's saying:

  mount: mounting root on /mnt failed: No such device

No idea what I'm doing wrong, "no such device" is not an informative
error message.

There's no obvious way to get the Linux client to tell me what tags
are available.  "What can I mount?  Do you see anything?"  I've
looked under /proc and /sys for "virtio"...  It's entirely possible
I'm missing something in my kernel .config but who knows what?

I note that qemu was sitting down and SULKING unless I specified the
security_model (I'm mounting read only, I don't care, but there
doesn't seem to be any way to DO a read-only export).  I'm guessing
based on the fact it stopped complaining that it is in fact exporting
something (and thus not upset I gave it a relative path, although giving
it an absolute path made no difference...)

Any clues?

Rob

             reply	other threads:[~2011-04-24 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 19:31 Rob Landley [this message]
2011-04-25  9:22 ` [Qemu-devel] virtfs error reporting? M. Mohan Kumar
2011-04-25 21:24 ` Eric Van Hensbergen

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=4DB47A9A.5050504@parallels.com \
    --to=rlandley@parallels.com \
    --cc=ericvh@gmail.com \
    --cc=qemu-devel@nongnu.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.