From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50605) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEI0T-0001S1-74 for qemu-devel@nongnu.org; Mon, 25 Apr 2011 05:23:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QEI0R-0004dH-MA for qemu-devel@nongnu.org; Mon, 25 Apr 2011 05:23:01 -0400 Received: from e23smtp05.au.ibm.com ([202.81.31.147]:58697) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEI0Q-0004aq-Ts for qemu-devel@nongnu.org; Mon, 25 Apr 2011 05:22:59 -0400 Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [202.81.31.245]) by e23smtp05.au.ibm.com (8.14.4/8.13.1) with ESMTP id p3P9GkF6007658 for ; Mon, 25 Apr 2011 19:16:46 +1000 Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p3P9MboV2277550 for ; Mon, 25 Apr 2011 19:22:39 +1000 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p3P9Ma91007431 for ; Mon, 25 Apr 2011 19:22:36 +1000 From: "M. Mohan Kumar" Date: Mon, 25 Apr 2011 14:52:33 +0530 References: <4DB47A9A.5050504@parallels.com> In-Reply-To: <4DB47A9A.5050504@parallels.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_Z1TtNAd+oAH7wLu" Content-Transfer-Encoding: 7bit Message-Id: <201104251452.33929.mohan@in.ibm.com> Subject: Re: [Qemu-devel] virtfs error reporting? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Eric Van Hensbergen , Rob Landley --Boundary-01=_Z1TtNAd+oAH7wLu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Monday 25 April 2011 1:01:38 am Rob Landley wrote: > 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? You can get available tags from /sys/devices/virtio-pci/virtio*/mount_tag > > 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 ---- M. Mohan Kumar --Boundary-01=_Z1TtNAd+oAH7wLu Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit

On Monday 25 April 2011 1:01:38 am Rob Landley wrote:

> 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?

You can get available tags from

/sys/devices/virtio-pci/virtio*/mount_tag

> 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

----

M. Mohan Kumar

--Boundary-01=_Z1TtNAd+oAH7wLu--