From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53698) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE2mZ-0006er-3m for qemu-devel@nongnu.org; Wed, 21 Jan 2015 16:25:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YE2mU-00053v-00 for qemu-devel@nongnu.org; Wed, 21 Jan 2015 16:25:47 -0500 Received: from indium.canonical.com ([91.189.90.7]:43353) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE2mT-00053G-Mh for qemu-devel@nongnu.org; Wed, 21 Jan 2015 16:25:41 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1YE2mS-0007PJ-Mt for ; Wed, 21 Jan 2015 21:25:40 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id A39E42E8026 for ; Wed, 21 Jan 2015 21:25:40 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 21 Jan 2015 21:16:42 -0000 From: neil prideaux Sender: bounces@canonical.com References: <20141219153639.25009.84583.malonedeb@wampee.canonical.com> Message-Id: <20150121211642.550.82493.malone@chaenomeles.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1404278] Re: tap connections not working on windows host Reply-To: Bug 1404278 <1404278@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I also confirm the problem on Windows 7 host. I tried the following over the past few nights: Downloaded the OpenVPN tap 32 adapter. Installed it and gave it a different= network address (192.168.200.10) to my normal LAN (192.168.1.10). Bridged = the 2 connections, which gets me a new IP via DHCP at the bridge (192.168.1= .101). = Got latest QEMU 2.2.0 for Windows from \lassauge.free.fr. Got linux images from https://people.debian.org/~aurel32/qemu/armel/ and us= ed the command as per the instructions there. Further added the -net tap sw= ithches to the cmd line, similar to above. Debian guest boots up ok, but TAP networking is not happening, no matter what combinations or permutations i've tried to configure the guest net iface. On the other hand, I obtained dsl-4.4.10-embedded.zip which comes with its own QEMU from http://ftp.heanet.ie/mirrors/damnsmalllinux.org/current/. After changing the command line to start QEMU with the -tap switch, and configuring dsl for dhcp, i was up and running immediately (automagically obtained its own ip as my host network as 192.168.1.102, same gateway as host network, pings ok in either direction, even pings google.com). This proves the tap adapter and bridge is configured correctly on the host side, and the supplied QEMU version works ok - can't tell exactly which QEMU version but it is circa 2006. After this attempt i've tried other versions of QEMU 1.6.0, and 1.1.1 with the same debian client still the same problem. i.e. boots up ok except for the TAP networking. It is most likely a QEMU problem, but i am amazed at the number of blog posts of ppl claiming it to be working. It is unlikely they used a recent QEMU version. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1404278 Title: tap connections not working on windows host Status in QEMU: New Bug description: using latest qemu 2.2.0 64bit for windows host (installed from qemu-w64-setup-20141210.exe obtained from http://qemu.weilnetz.de/w64/ ),OpenVPN 2.6.3-I601 64bit tap adapter named tap01 and calling qemu using the following. qemu-system-x86_64.exe -m 512 -net nic -net tap,ifname=3Dtap01 -hda "c:\\data\\images\\test.img" where the image contains a slackware 14.0 64bit install. The tap is bridged with the real network adapter and the bridge is given = an ip of 10.1.1.41 (which works as the ip for the windows host). The tap ad= apter (in network connections) shows connected when the qemu vm is running.= inside the vm, the network is given an ip of 10.1.1.143 (the netmask and d= efault gateway are the same for the virtual and real pc). fault. The vm cannot see the rest of the local network or visa-versa. This used = to work in early (0.9 32bit) versions of qemu. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1404278/+subscriptions