xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Bob Liu <bob.liu@oracle.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	David Vrabel <david.vrabel@citrix.com>
Subject: Re: [RFC] VirtFS support on Xen
Date: Sat, 23 Jan 2016 14:50:30 +0000	[thread overview]
Message-ID: <20160123145030.GA9393@citrix.com> (raw)
In-Reply-To: <56A310B4.3080808@oracle.com>

On Sat, Jan 23, 2016 at 01:33:40PM +0800, Bob Liu wrote:
> 
> On 01/22/2016 06:50 PM, Wei Liu wrote:
> > On Fri, Jan 22, 2016 at 06:45:30PM +0800, Bob Liu wrote:
> >> Hi Wei,
> >>
> >> On 01/21/2016 06:59 PM, Wei Liu wrote:
> >>> On Thu, Jan 21, 2016 at 10:50:08AM +0000, David Vrabel wrote:
> >>>> On 21/01/16 10:28, Wei Liu wrote:
> >>>>> [RFC] VirtFS support on Xen
> >>>>>
> >>>>> # Introduction
> >>>>>
> >>>>> QEMU/KVM supports file system passthrough via an interface called
> >>>>> VirtFS [0]. VirtFS is in turn implemented with 9pfs protocol [1] and
> >>>>> VirtIO transport.
> >>>>>
> >>>>> Xen used to have its own implementation of file system passthrough
> >>>>> called XenFS, but that has been inactive for a few years. The latest
> >>>>> update was in 2009 [2].
> >>>>>
> >>>>> This project aims to add VirtFS support on Xen. This is more
> >>>>> sustainable than inventing our own wheel.#
> >>>>
> >>>> What's the use case for this?  Who wants this feature?
> >>>>
> >>>
> >>> Anyone who wants file system passthrough.  More specifically, VM-based
> >>> container solutions can share files from host file system.
> >>>
> >>
> >> I'm a bit confused, can't we just use the VirtFS of Qemu?
> >> E.g
> >> ./configure --with-extra-qemuu-configure-args="--enable-virtfs"
> >>
> > 
> > Yes, in theory you can -- with VirtIO transport. But I'm not sure if
> > Virtio has been fixed to work with Xen.  That also means you need QEMU
> > emulation, which we don't really need (or want) when running in PV or
> > PVH mode.
> > 
> 
> Just make sure if I get it right, in the KVM case:
> Linux guest(v9fs-client) -> VirtIO transport -> Qemu(v9fs-server) -> Local file system in Host
> 
> And your plan is:
> DomU(v9fs-client) -> XEN transport:grant map based -> Qemu(v9fs-server) -> Local file system in Dom0
> 

Yes. Your understanding is correct.

> Which means we need to implement a XEN-transport in linux/net/9p/, and also make Qemu can recognize this transport because we need Qemu to run as the v9fs-server anyway?
> 

Yes. There will be code in both QEMU and Linux kernel.

Wei.

> Bob

  reply	other threads:[~2016-01-23 14:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 10:28 [RFC] VirtFS support on Xen Wei Liu
2016-01-21 10:50 ` David Vrabel
2016-01-21 10:59   ` Wei Liu
2016-01-22 10:45     ` Bob Liu
2016-01-22 10:50       ` Wei Liu
2016-01-22 11:12         ` Paul Durrant
2016-01-22 11:31           ` Wei Liu
2016-01-23  5:33         ` Bob Liu
2016-01-23 14:50           ` Wei Liu [this message]
2016-01-23 15:35             ` Konrad Rzeszutek Wilk
2016-01-25 11:29               ` Wei Liu
2016-01-25 11:35                 ` David Vrabel
2016-01-25 15:13                   ` Wei Liu

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=20160123145030.GA9393@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=bob.liu@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=xen-devel@lists.xenproject.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).