From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CjtEt-000803-0u for qemu-devel@nongnu.org; Thu, 30 Dec 2004 00:52:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CjtEs-0007zr-It for qemu-devel@nongnu.org; Thu, 30 Dec 2004 00:52:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CjtEs-0007zo-H8 for qemu-devel@nongnu.org; Thu, 30 Dec 2004 00:52:46 -0500 Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cjt3Y-0003J7-FS for qemu-devel@nongnu.org; Thu, 30 Dec 2004 00:41:04 -0500 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Cjt3W-0006ek-00 for ; Thu, 30 Dec 2004 06:41:02 +0100 Received: from inet.ycc.ru ([217.148.52.177]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Dec 2004 06:41:02 +0100 Received: from patrakov by inet.ycc.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Dec 2004 06:41:02 +0100 From: "Alexander E. Patrakov" Date: Thu, 30 Dec 2004 10:41:51 +0500 Message-ID: References: <001401c4ee1c$5e440eb0$0102000a@freelance> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Sender: news Subject: [Qemu-devel] Re: Qemu port on Windows to support tun/tap Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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