From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Trying to emulate an openmosix cluster
Date: Wed, 28 Sep 2005 21:31:54 +0200 [thread overview]
Message-ID: <46d6db660509281231671b233b@mail.gmail.com> (raw)
In-Reply-To: <46d6db6605092214567b1611f2@mail.gmail.com>
I managed doing this simulation using Parallels Workstation
(I'm not trying to spam the list here...).
It worked flawlessly, using bridged networking on a dedicated
TAP-like network device...
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
On 9/22/05, Christian MICHON <christian.michon@gmail.com> wrote:
(...)
> Guests are openmosix linux nodes done by:
> http://www.purehacking.com/chaos/iso/chaos-1.6.iso
(...)
next prev parent reply other threads:[~2005-09-28 19:34 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 ` Christian MICHON [this message]
2005-09-28 22:54 ` [Qemu-devel] " Jim C. Brown
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=46d6db660509281231671b233b@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).