From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Qemu port on Windows to support tun/tap
Date: Thu, 30 Dec 2004 21:50:06 +0800 [thread overview]
Message-ID: <001201c4ee76$7bfa0130$0102000a@freelance> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 921 bytes --]
>> 1. If I start up second instance of guest OS, it will not join the
>> network. Looks like
>> somewhere there is a limitation on single open.
>>
>> 2. And I can't have multiple network cards within one guest OS using the
>> tap devices.
>>
>> Anyway, I view this as the current limitation of the software. Until
>> changes made to improving it, I will have to live with this limitation.
>
> When you try to use multiple instances of qemu on tun/tap network, you must
>make sure that each virtual machine gets its own MAC address.
>
>qemu -macaddr 52:54:00:12:34:56 ....
>qemu -macaddr 52:54:00:12:34:57 ....
>
>Here 52:54:00 is Realtek and 12:34:56 is what you can change.
I did that when I performed the testing, because I found all these
things to be working perfectly on Linux host. I am just not able
to get it working with windows port combined with tap-win32 driver.
Cheers
[-- Attachment #1.2: Type: text/html, Size: 1883 bytes --]
[-- Attachment #2: InterScan_SafeStamp.txt --]
[-- Type: text/plain, Size: 250 bytes --]
****** Message from InterScan E-Mail VirusWall NT ******
** No virus found in attached file noname.htm
** No virus found in attached file noname.htm
This mail has been scanned by InterScan.
***************** End of message ***************
next reply other threads:[~2004-12-30 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 13:50 Ming-Ching Tiew [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 14:29 [Qemu-devel] Re: Qemu port on Windows to support tun/tap Ming-Ching Tiew
2004-12-30 3:05 [Qemu-devel] " Ming-Ching Tiew
2004-12-30 5:41 ` [Qemu-devel] " Alexander E. Patrakov
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='001201c4ee76$7bfa0130$0102000a@freelance' \
--to=mingching.tiew@redtone.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).