qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Gamal <m.gamal005@gmail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Cam Macdonell <cam@cs.ualberta.ca>,
	qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
	Javier Guerra Giraldez <javier@guerrag.com>
Subject: Re: [Qemu-devel] [GSoC 2010] Pass-through filesystem support.
Date: Sat, 10 Apr 2010 14:42:30 +0200	[thread overview]
Message-ID: <u2q52d4a3891004100542m365d743bxb09011a549517704@mail.gmail.com> (raw)
In-Reply-To: <20100410121247.GA18080@shareable.org>

On Sat, Apr 10, 2010 at 2:12 PM, Jamie Lokier <jamie@shareable.org> wrote:
> Mohammed Gamal wrote:
>> Hi Javier,
>> Thanks for the link. However, I'm still concerned with
>> interoperability with other operating systems, including non-Windows
>> ones. I am not sure of how many operating systems actually support 9p,
>> but I'm almost certain that CIFS would be more widely-supported.
>> I am still a newbie as far as all this is concerned, so if anyone has
>> any arguments as to whether which approach should be taken, I'd be
>> enlightened to hear them.
>
> To throw a spanner in, the most widely supported filesystem across
> operating systems is probably NFS, version 2 :-)
>
> -- Jamie
>

Remember that Windows usage on a VM is not some rare use case, and
it'd be a little bit of a pain from a user's perspective to have to
install a third party NFS client for every VM they use. Having
something supported on the VM out of the box is a better option IMO.

Regards,
Mohammed

  reply	other threads:[~2010-04-10 12:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 16:01 [Qemu-devel] [GSoC 2010] Pass-through filesystem support Mohammed Gamal
2010-04-08 16:02 ` [Qemu-devel] " Mohammed Gamal
2010-04-08 16:23   ` Stefan Hajnoczi
2010-04-09 13:18 ` [Qemu-devel] " Luiz Capitulino
2010-04-09 17:11   ` jvrao
2010-04-09 17:23     ` Mohammed Gamal
2010-04-09 21:22 ` Jamie Lokier
2010-04-09 22:17   ` Mohammed Gamal
2010-04-09 22:22     ` Javier Guerra Giraldez
2010-04-09 22:34       ` Mohammed Gamal
2010-04-10 12:12         ` Jamie Lokier
2010-04-10 12:42           ` Mohammed Gamal [this message]
2010-04-11  0:35             ` Javier Guerra Giraldez
2010-04-11 22:29               ` Jamie Lokier
2010-04-12  8:15                 ` Mohammed Gamal
2010-04-12  8:59                   ` Alexander Graf
2010-04-12 12:04                     ` Jamie Lokier
2010-04-12 12:10                       ` Alexander Graf
2010-04-12 11:58                   ` Jamie Lokier
2010-04-12 12:14                     ` Alexander Graf
2010-04-12 15:43                       ` jvrao
2010-04-13 19:08                         ` jvrao
2010-04-13 20:17                           ` Mohammed Gamal
2010-04-19 22:54                             ` jvrao
2010-04-20  4:26                               ` Mohammed Gamal
2010-04-20 18:36                                 ` jvrao
2010-04-21  4:20                                   ` Mohammed Gamal
2010-04-21  6:33                                     ` jvrao
2010-04-12 15:16   ` jvrao

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=u2q52d4a3891004100542m365d743bxb09011a549517704@mail.gmail.com \
    --to=m.gamal005@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=cam@cs.ualberta.ca \
    --cc=jamie@shareable.org \
    --cc=javier@guerrag.com \
    --cc=kvm@vger.kernel.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).