From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Qemu port on Windows to support tun/tap
Date: Thu, 30 Dec 2004 10:41:51 +0500 [thread overview]
Message-ID: <cr04d0$mn2$1@sea.gmane.org> (raw)
In-Reply-To: 001401c4ee1c$5e440eb0$0102000a@freelance
Ming-Ching Tiew wrote:
>
>> 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.
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.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2004-12-30 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 3:05 [Qemu-devel] Qemu port on Windows to support tun/tap Ming-Ching Tiew
2004-12-30 5:41 ` Alexander E. Patrakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 13:50 [Qemu-devel] " Ming-Ching Tiew
2004-12-30 14:29 Ming-Ching Tiew
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='cr04d0$mn2$1@sea.gmane.org' \
--to=patrakov@ums.usu.ru \
--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).