From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kevin Zhao <kevin.zhao@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [Help]: Does qemu-system-aarch64 support virtio-9p? I got a problem when remap host file to guest in AArch64.
Date: Fri, 5 Aug 2016 09:28:57 +0100 [thread overview]
Message-ID: <20160805082857.GH9933@redhat.com> (raw)
In-Reply-To: <CAN76PtTfrRFDNDXHFiOvavk4EkOqdXvfKOYJh5AmZPzErxmOkw@mail.gmail.com>
On Fri, Aug 05, 2016 at 10:23:58AM +0800, Kevin Zhao wrote:
> Hi All,
> I have a problem may about Qemu and kindly need your help. Does
> qemu-system-aarch64 support virtio-9p ?
> Recently I have tried to use qemu remapped the file from host to
> guest. As I know, Qemu has supported this so long as guest kernel has
> support 9p(virtfs). Reference to this link:
> http://wiki.qemu.org/Documentation/9psetup
> Fedora 24 AArch64 kernel has supported this:
> [root@sha-win-225 ~]# lsmod | grep 9p
> 9p 56273 0
> fscache 87449 1 9p
> 9pnet_virtio 9122 0
> 9pnet 83564 2 9p,9pnet_virtio
> virtio_ring 13866 5 virtio_net,virtio_pci,9pnet_
> virtio,virtio_mmio,virtio_scsi
> virtio 9467 5 virtio_net,virtio_pci,9pnet_
> virtio,virtio_mmio,virtio_scsi
>
> Now I use virsh to launch the VM, and the corresponding qemu command I
> have pasted here:
> http://paste.openstack.org/show/549225/.
> You can see that:
> * -fsdev
> local,security_model=mapped,id=fsdev-fs0,path=/var/lib/libvirt/images/coreos
> -device
> virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=share,bus=pci.2,addr=0x1*
> Here is the command that remapped the directory from host to guest.
> After VM launched, I use the command to mount:
> * mount -t 9p -o trans=virtio share /tmp/shared/
> -oversion=9p2000.L,posixacl,cache=loose*
> But mount command will be blocked and output nothing.
Try using version=9p2000.u instead - I've noticed other versions have
been buggy in various kernel version/qemu version combinations. The
9p2000.u version is what i use in libvirt-sandobx and so I know it will
work in general.
> The Qemu version is QEMU emulator version 2.5.0 (Debian
> 1:2.5+dfsg-5ubuntu10.2). Besides test fedora24 guest, I have got the same
> problem in Debian jessie.
> Kindly need your help~You will be really appreciated.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-08-05 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 2:23 [Qemu-devel] [Help]: Does qemu-system-aarch64 support virtio-9p? I got a problem when remap host file to guest in AArch64 Kevin Zhao
2016-08-05 8:13 ` Peter Maydell
2016-08-05 10:09 ` Kevin Zhao
2016-08-05 8:28 ` Daniel P. Berrange [this message]
2016-08-05 10:08 ` Kevin Zhao
2016-08-05 10:27 ` Claudio Fontana
2016-08-05 10:32 ` Claudio Fontana
2016-08-05 13:18 ` Kevin Zhao
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=20160805082857.GH9933@redhat.com \
--to=berrange@redhat.com \
--cc=kevin.zhao@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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 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).