From: jvrao <jvrao@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Cam Macdonell <cam@cs.ualberta.ca>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [GSoC 2010] Pass-through filesystem support.
Date: Fri, 09 Apr 2010 10:11:32 -0700 [thread overview]
Message-ID: <4BBF5FC4.2090200@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100409101836.526762c8@redhat.com>
Luiz Capitulino wrote:
> On Thu, 8 Apr 2010 18:01:01 +0200
> Mohammed Gamal <m.gamal005@gmail.com> wrote:
>
>> Hi,
>> Now that Cam is almost done with his ivshmem patches, I was thinking
>> of another idea for GSoC which is improving the pass-though
>> filesystems.
>> I've got some questions on that:
>>
>> 1- What does the community prefer to use and improve? CIFS, 9p, or
>> both? And which is better taken up for GSoC.
Please look at our recent set of patches.
We are developing a 9P server for QEMU and client is already part of mainline Linux.
Our goal is to optimize it for virualization environment and will work as FS pass-through
mechanism between host and the guest.
Here is the latest set of patches..
http://www.mail-archive.com/qemu-devel@nongnu.org/msg29267.html
Please let us know if you are interested ... we can coordinate.
Thanks,
JV
>>
>> 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?
>>
>> 3- In addition, I see the idea mentions that some Windows code needs
>> to be written to use network shares on a special interface. What's
>> that interface? And what's the nature of that Windows code? (a driver
>> a la "guest additions"?)
>
> CC'ing Aneesh as he's working on that.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: jvrao <jvrao@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, aneesh.kumar@linux.vnet.ibm.com,
Mohammed Gamal <m.gamal005@gmail.com>,
Cam Macdonell <cam@cs.ualberta.ca>
Subject: Re: [Qemu-devel] [GSoC 2010] Pass-through filesystem support.
Date: Fri, 09 Apr 2010 10:11:32 -0700 [thread overview]
Message-ID: <4BBF5FC4.2090200@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100409101836.526762c8@redhat.com>
Luiz Capitulino wrote:
> On Thu, 8 Apr 2010 18:01:01 +0200
> Mohammed Gamal <m.gamal005@gmail.com> wrote:
>
>> Hi,
>> Now that Cam is almost done with his ivshmem patches, I was thinking
>> of another idea for GSoC which is improving the pass-though
>> filesystems.
>> I've got some questions on that:
>>
>> 1- What does the community prefer to use and improve? CIFS, 9p, or
>> both? And which is better taken up for GSoC.
Please look at our recent set of patches.
We are developing a 9P server for QEMU and client is already part of mainline Linux.
Our goal is to optimize it for virualization environment and will work as FS pass-through
mechanism between host and the guest.
Here is the latest set of patches..
http://www.mail-archive.com/qemu-devel@nongnu.org/msg29267.html
Please let us know if you are interested ... we can coordinate.
Thanks,
JV
>>
>> 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?
>>
>> 3- In addition, I see the idea mentions that some Windows code needs
>> to be written to use network shares on a special interface. What's
>> that interface? And what's the nature of that Windows code? (a driver
>> a la "guest additions"?)
>
> CC'ing Aneesh as he's working on that.
>
>
next prev parent reply other threads:[~2010-04-09 17:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 16:01 [GSoC 2010] Pass-through filesystem support Mohammed Gamal
2010-04-08 16:01 ` [Qemu-devel] " Mohammed Gamal
2010-04-08 16:02 ` Mohammed Gamal
2010-04-08 16:02 ` [Qemu-devel] " Mohammed Gamal
2010-04-08 16:23 ` Stefan Hajnoczi
2010-04-08 16:23 ` [Qemu-devel] " Stefan Hajnoczi
2010-04-09 13:18 ` [Qemu-devel] " Luiz Capitulino
2010-04-09 17:11 ` jvrao [this message]
2010-04-09 17:11 ` jvrao
2010-04-09 17:23 ` Mohammed Gamal
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:22 ` Javier Guerra Giraldez
2010-04-09 22:34 ` Mohammed Gamal
2010-04-09 22:34 ` Mohammed Gamal
2010-04-10 12:12 ` Jamie Lokier
2010-04-10 12:12 ` Jamie Lokier
2010-04-10 12:42 ` Mohammed Gamal
2010-04-10 12:42 ` Mohammed Gamal
2010-04-11 0:35 ` Javier Guerra Giraldez
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:15 ` Mohammed Gamal
2010-04-12 8:59 ` Alexander Graf
2010-04-12 8:59 ` Alexander Graf
2010-04-12 12:04 ` Jamie Lokier
2010-04-12 12:04 ` Jamie Lokier
2010-04-12 12:10 ` Alexander Graf
2010-04-12 12:10 ` Alexander Graf
2010-04-12 11:58 ` Jamie Lokier
2010-04-12 11:58 ` Jamie Lokier
2010-04-12 12:14 ` Alexander Graf
2010-04-12 12:14 ` Alexander Graf
2010-04-12 15:43 ` jvrao
2010-04-12 15:43 ` jvrao
2010-04-13 19:08 ` jvrao
2010-04-13 20:17 ` Mohammed Gamal
2010-04-13 20:17 ` Mohammed Gamal
2010-04-19 22:54 ` jvrao
2010-04-20 4:26 ` Mohammed Gamal
2010-04-20 4:26 ` [Qemu-devel] " 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
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=4BBF5FC4.2090200@linux.vnet.ibm.com \
--to=jvrao@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cam@cs.ualberta.ca \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=m.gamal005@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.