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: Thu, 30 Dec 2004 11:05:02 +0800 [thread overview]
Message-ID: <001401c4ee1c$5e440eb0$0102000a@freelance> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 963 bytes --]
> 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 ?
OK I got it partially working now. Looks like the name is not the "device driver" name,
but rather, the arbitrary network interface name assigned during the installation,
which is normally it the form of "Local Area Connection x". I renamed and matched it
accordingly, then the above works. I could now ping between the guest OS and
host OS.
But still there are other problems, such as :-
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.
Cheers.
[-- Attachment #1.2: Type: text/html, Size: 2928 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 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 3:05 Ming-Ching Tiew [this message]
2004-12-30 5:41 ` [Qemu-devel] Re: Qemu port on Windows to support tun/tap Alexander E. Patrakov
-- strict thread matches above, loose matches on Subject: below --
2004-12-29 4:32 [Qemu-devel] " 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='001401c4ee1c$5e440eb0$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).