From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BkZXl-00071X-Bx for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:30:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BkZXk-00071L-SE for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:30:49 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BkZXk-00071B-OW for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:30:48 -0400 Received: from [38.113.3.61] (helo=babyruth.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BkZVF-0004u7-Hh for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:28:13 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by babyruth.hotpop.com (Postfix) with SMTP id D79C16D8C28 for ; Wed, 14 Jul 2004 01:42:22 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-2.hotpop.com (Postfix) with ESMTP id 3369E6D86DB for ; Wed, 14 Jul 2004 01:40:25 +0000 (UTC) Date: Tue, 13 Jul 2004 22:26:11 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Win98: how to exchange data with Linux Message-ID: <20040714022611.GB6436@jbrown.mylinuxbox.org> References: <200407122356.02502.eschmit@tin.it> <1089671145.12301.10.camel@aragorn> <200407130924.58879.vaise@votreservice.com> <1089727701.7843.58.camel@espiron.av7.local> <40F3EF20.2020802@kadu.net> <40F3F5B1.2040908@kadu.net> <40F41A65.8050807@volny.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40F41A65.8050807@volny.cz> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, Jul 13, 2004 at 07:22:45PM +0200, Filip Navara wrote: > Adrian Smarzewski wrote: > [snip] > > >It's a windows nt driver for ext2 partitions. maybe we could > >change it so instead of writting files on real drive it will > >pass commands to qemu? file system is not so important, but > >this driver is lgpl'ed. > > At first guys, you confuse file system drivers and storage drivers. The > file system drivers have de facto no knowledge on which disk are the > data located, (on Windows) they recieve an object and send Read/Write > requests to it (well, basicly, in reality there's also the cache manager > between them). At second, the idea can't work, even if you would have a > storage driver that uses some backdoor I/O port to access host disk, the > host OS can't access the same partition at the same time due to things > like caching (on both sides (guest/host)). > > - Filip > > Technically speaking, one could write a file system driver that talks to qemu instead of going through a storage driver. (I didn't say it would be easy, just barely possible.) Qemu could then translate attempts (to write a file on Windows using this driver would cause qemu to write the file on linux's fs natively for example). It is more work than its worth, but it is possible. A modified user-net which emulated SMB protocol to the guest but did the i/o natively on the host would do the same thing and be easier to implement. Setting up tuntap or VDE is easiest of all. :) > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.