From: "Jim C. Brown" <jma5@umd.edu>
To: Christian MICHON <christian.michon@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Trying to emulate an openmosix cluster
Date: Wed, 28 Sep 2005 18:54:21 -0400 [thread overview]
Message-ID: <20050928225421.GA5804@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <46d6db660509281231671b233b@mail.gmail.com>
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.
prev parent reply other threads:[~2005-09-28 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 21:56 [Qemu-devel] Trying to emulate an openmosix cluster Christian MICHON
2005-09-28 19:31 ` [Qemu-devel] " Christian MICHON
2005-09-28 22:54 ` Jim C. Brown [this message]
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=20050928225421.GA5804@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=christian.michon@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.