Am 25.03.2017 um 00:46 schrieb Andrew Baumann:
The docs generally steer users away from using the legacy -net parameter, however on win32 attempting to enable a tap device using -netdev tap fails at an abort() in tap_enable(). Removing the abort()s seems to be enough to get everything working, so do that.Signed-off-by: Andrew Baumann <andrew.baum...@microsoft.com> --- net/tap-win32.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/net/tap-win32.c b/net/tap-win32.c index 662f9b6..3620843 100644 --- a/net/tap-win32.c +++ b/net/tap-win32.c @@ -811,10 +811,10 @@ int net_init_tap(const Netdev *netdev, const char *name, int tap_enable(NetClientState *nc) { - abort(); + return 0; } int tap_disable(NetClientState *nc) { - abort(); + return 0; }
As I never worked with TAP on Windows, I cannot say much to this fix. Jason, what is the use of tap_enable, tap_disable? Is it fine to simply do nothing on Windows here? And is this something for QEMU 2.9 (I added question to subject line)? Stefan
