From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu port on Windows to support tun/tap
Date: Wed, 29 Dec 2004 12:32:29 +0800 [thread overview]
Message-ID: <002c01c4ed5f$6850fa70$8916fea9@freelance> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 950 bytes --]
>> I don't seem to be able to get it working and there is no mention
>> it at all in the docs.
>>
>
>A patch for this was posted on the list some time ago:
>http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00213.html
I downloaded it and compiled it without problem, but it does not seem
to work. What I did is this, I added one Tap-Win32 V8 adator, configure
an IP to it, then I started two instances of my guest OS which is Linux.
Then I configure them in the same network. Try to ping OS Tap IP
and the other guest OS's IP, none responded to the ping. I started it
this way :-
qemu.exe -L .\bios -nics 1 -tap tap0801 -m 8 -boot a -fda linux.img -enable-audio -localtime
Is the name "tap0801" correct ?
Furthermore, what if I want to have multiple network cards ? How to
assign which network card connects to which tap device instance ?
Hmmm looks like what I need is a port of vde on Windows ....
Cheers
[-- Attachment #1.2: Type: text/html, Size: 2267 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-29 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 4:32 Ming-Ching Tiew [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 3:05 [Qemu-devel] Qemu port on Windows to support tun/tap Ming-Ching Tiew
2004-12-28 8:43 Ming-Ching Tiew
2004-12-28 8:57 ` Lars Munch
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='002c01c4ed5f$6850fa70$8916fea9@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).