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>
Subject: Re: [Qemu-devel] [GSoC 2010] Pass-through filesystem support.
Date: Sat, 10 Apr 2010 00:17:30 +0200	[thread overview]
Message-ID: <q2w52d4a3891004091517ye107162cm15476fce5157a038@mail.gmail.com> (raw)
In-Reply-To: <20100409212212.GB31666@shareable.org>

On Fri, Apr 9, 2010 at 11:22 PM, Jamie Lokier <jamie@shareable.org> wrote:
> Mohammed Gamal wrote:
>> 2- With respect to CIFS. I wonder how the shares are supposed to be
>> exposed to the guest. Should the Samba server be modified to be able
>> to use unix domain sockets instead of TCP ports and then QEMU
>> communicating on these sockets. With that approach, how should the
>> guest be able to see the exposed share? And what is the problem of
>> using Samba with TCP ports?
>
> One problem with TCP ports is it only works when the guest's network
> is up :) You can't boot from that.  It also makes things fragile or
> difficult if the guest work you are doing involves fiddling with the
> network settings.
>
> Doing it over virtio-serial would have many benefits.
>
> On the other hand, Samba+TCP+CIFS does have the advantage of working
> with virtually all guest OSes, including Linux / BSDs / Windows /
> MacOSX / Solaris etc.  9P only works with Linux as far as I know.
>
> I big problem with Samba at the moment is it's not possible to
> instantiate multiple instances of Samba any more, and not as a
> non-root user.  That's because it contains some hard-coded paths to
> directories of run-time state, at least on Debian/Ubuntu hosts where I
> have tried and failed to use qemu's smb option, and there is no config
> file option to disable that or even change all the paths.
>
> Patching Samba to make per-user instantiations possible again would go
> a long way to making it useful for filesystem passthrough.  Patching
> it so you can turn off all the fancy features and have it _just_ serve
> a filesystem with the most basic necessary authentication would be
> even better.
>
> -- Jamie
>

Hi Jamie,

Thanks for your input.

That's all good and well. The question now is which direction would
the community prefer to go. Would everyone be just happy with
virtio-9p passthrough? Would it support multiple OSs (Windows comes to
mind here)? Or would we eventually need to patch Samba for passthrough
filesystems?

Regards,
Mohammed

  reply	other threads:[~2010-04-09 22:17 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 [this message]
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
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=q2w52d4a3891004091517ye107162cm15476fce5157a038@mail.gmail.com \
    --to=m.gamal005@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=cam@cs.ualberta.ca \
    --cc=jamie@shareable.org \
    --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).