From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GAmBJ-0001D4-PR for qemu-devel@nongnu.org; Wed, 09 Aug 2006 07:25:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GAmBG-0001BZ-Pu for qemu-devel@nongnu.org; Wed, 09 Aug 2006 07:25:00 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GAmBG-0001BT-KP for qemu-devel@nongnu.org; Wed, 09 Aug 2006 07:24:58 -0400 Received: from [64.233.166.182] (helo=py-out-1112.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GAmFw-0002ah-8Y for qemu-devel@nongnu.org; Wed, 09 Aug 2006 07:29:48 -0400 Received: by py-out-1112.google.com with SMTP id c63so330300pyc for ; Wed, 09 Aug 2006 04:24:57 -0700 (PDT) Date: Wed, 9 Aug 2006 14:24:49 +0300 From: Paul Sokolovsky Message-ID: <17610573946.20060809142449@gmail.com> Subject: Re: [Qemu-devel] Bug of Qemu when running TAP device on Windows? In-Reply-To: <20060809083151.61674.qmail@web38112.mail.mud.yahoo.com> References: <20060809083151.61674.qmail@web38112.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Reply-To: Paul Sokolovsky , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tieu Ma Dau

Hello Tieu,

Do you think that posting same long mail sev= eral times will get you more answers than careful reading of docs/some thou= ght? ;-)

Wednesday, August 9, 2006, 11:31:51 AM, you wrote:

Hi all,

I ran successfully Qemu to simulate ARM system on Li= nux host with the following command:

./qemu-system-arm -kernel zImage.integratorCP -appen= d "root=3D/dev/nfs nfsroot=3D192.168.7.1:/mnt/nfsqemu rw ip=3D192.168.7.2::= 192.168.7.1:255.255.255.0 " -net nic,vlan=3D0 -net tap,vlan=3D0,ifname=3Dta= p0,script=3D./qemu-ifup

The content of qemu-ifup script is:

ifconfig tap0 192.168.7.1

>	But my project demands me to run this ARM system on = Windows host. So I modify a bit the qemu-ifup script as: ipconfig tap0 192.168.7.1 # "ipconfig" , not "ifconf= ig"

Cool solution, but did you try to run that o= n your own?

>	And the corresponding command on Windows is:<= /p> qemu-system-arm -kernel zImage.integrator -append "r= oot=3D/dev/nfs nfsroot=3D192. 168.7.1:/c/cygwin/openpsionfiltered=3D192.168.7.2::1= 92.168.7.1:255.255.255.0" -net nic,vlan=3D0 -net tap,vlan=3D0,ifname=3Dtap0,script= =3D./qemu-ifup

Ok, so QEMU under Windows is a bit unlike Li= nux. There, ifname is what you see in "Network connections", something long= incomprehensible like "Local area network connection #N". Be especially wa= ry of localized names. So, you better rename it to contain ASCII only. You = can even rename it to "tap0". Also, Windows TAP doesn't require "script" - = after all, you set connection's parameters with right-clicking on it, and i= t's being "upped" automagically on client start (but yes, you can leave it = there; that way (assuming renaming conn to "tap0"), you can have portable s= tartup command line ;-) ).

I'm successfully running Linux/ARM in QEMU booting o= ff NFS in coLinux running on the same machine. Windows XP emulates router b= etween them ;-) : http://handhelds.org/hypermail/familiar/312/31225.html

Here's my command line:

qemu-system-arm.exe -L . -kernel zImage-2.6.16-qemuarm-20060525084= 935.bin -initrd bootstrap-image-bootchart-v0.8.4-rc3-h4000.rootfs.ext2.gz -= append "root=3D/dev/ram0 rw init=3D/sbin/bootchartd ramdisk_size=3D16384 ip= =3D192.168.30.2:192.168.30.1:192.168.30.1:255.255.255.0" -net nic,vlan=3D0 = -net tap,vlan=3D0,ifname=3D"TAP-qemu-arm"

Best regards,

Paul = mailto:pmiscml@gmail.com