[Bug 1404278] Re: tap connections not working on windows host

[Stefan Hajnoczi]

Varun Chitre: I'm not sure the fix was identified, but this one stood
out in the git log:

commit b73c1849148da1229a3c3b336311a8194970b35f
Author: Andrew Baumann <Andrew.Baumann@microsoft.com>
Date:   Wed Nov 18 11:45:09 2015 -0800

    tap-win32: disable broken async write path

-- 
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:
  Fix Released

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=tap01 -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 adapter 
(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 default 
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