From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O0E6o-0006Oh-EV for qemu-devel@nongnu.org; Fri, 09 Apr 2010 09:18:54 -0400 Received: from [140.186.70.92] (port=39662 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O0E6l-0006OC-Kn for qemu-devel@nongnu.org; Fri, 09 Apr 2010 09:18:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O0E6k-0003Xs-8e for qemu-devel@nongnu.org; Fri, 09 Apr 2010 09:18:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59587) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O0E6k-0003Xb-1F for qemu-devel@nongnu.org; Fri, 09 Apr 2010 09:18:50 -0400 Date: Fri, 9 Apr 2010 10:18:36 -0300 From: Luiz Capitulino Subject: Re: [Qemu-devel] [GSoC 2010] Pass-through filesystem support. Message-ID: <20100409101836.526762c8@redhat.com> In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mohammed Gamal Cc: Anthony Liguori , Cam Macdonell , qemu-devel@nongnu.org, kvm-devel , aneesh.kumar@linux.vnet.ibm.com On Thu, 8 Apr 2010 18:01:01 +0200 Mohammed Gamal 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. > > 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.