From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EKl3b-0006LC-OJ for qemu-devel@nongnu.org; Wed, 28 Sep 2005 19:09:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EKl3X-0006Je-H6 for qemu-devel@nongnu.org; Wed, 28 Sep 2005 19:09:46 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EKl3Q-0005pJ-19 for qemu-devel@nongnu.org; Wed, 28 Sep 2005 19:09:36 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EKkos-00070Q-Lf for qemu-devel@nongnu.org; Wed, 28 Sep 2005 18:54:34 -0400 Date: Wed, 28 Sep 2005 18:54:21 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Re: Trying to emulate an openmosix cluster Message-ID: <20050928225421.GA5804@jbrown.mylinuxbox.org> References: <46d6db6605092214567b1611f2@mail.gmail.com> <46d6db660509281231671b233b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46d6db660509281231671b233b@mail.gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christian MICHON , qemu-devel@nongnu.org On Wed, Sep 28, 2005 at 09:31:54PM +0200, Christian MICHON wrote: > My point is the following: today 2 qemu guests with dedicated > macaddr cannot share the same TAP-win32 v8 adapter. > > The software I mentionned above doesn't have similar limitation. > Would it be feasible to change the current tap/win32 patch to > overcome qemu's current limitation, and where to start ? > > Christian > IIRC the limitation is due to the OpenTap implementation of Windows itself. And thats probably a limitation inherited from elsewhere - the winpcap that Tap/win32 uses, if I understand correctly. Of course I can imagine one possibility. Basicially, use something akin to VDE: a master program is connected several instances of a modified qemu, so that qemu gets its ethernet packets from the master program and sends its own back to it. THe master program just does what vde_switch does: shuttle packets between the different qemu instances. Then you just need to get the master program to use winpcap or tap/win32 to be able to forward packets between the Windows host and the qemu guests. Nothing like that exists right now (at least nothing that I know of) for Windows - you will need to a) write it from scratch or b) port VDE to Windows. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.