From: neil prideaux <prideaux90@hotmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1404278] Re: tap connections not working on windows host
Date: Wed, 21 Jan 2015 21:16:42 -0000 [thread overview]
Message-ID: <20150121211642.550.82493.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20141219153639.25009.84583.malonedeb@wampee.canonical.com
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 used the command as per the instructions there. Further added the -net tap swithches 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=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
next prev parent reply other threads:[~2015-01-21 21:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 15:36 [Qemu-devel] [Bug 1404278] [NEW] tap connections not working on windows host timsoft
2014-12-19 21:09 ` [Qemu-devel] [Bug 1404278] " timsoft
2015-01-02 13:38 ` [Qemu-devel] [Bug 1404278] [NEW] " Stefan Hajnoczi
2015-01-05 17:11 ` [Qemu-devel] [Bug 1404278] " timsoft
2015-01-06 11:47 ` Stefan Hajnoczi
2015-01-06 21:12 ` timsoft
2015-01-07 9:06 ` Stefan Hajnoczi
2015-01-06 21:30 ` timsoft
2015-01-07 12:51 ` Stefan Hajnoczi
2015-01-07 16:09 ` timsoft
2015-03-24 11:10 ` Stefan Hajnoczi
2015-01-12 3:02 ` Tommy
2015-01-21 21:16 ` neil prideaux [this message]
2015-02-07 23:48 ` James J Myers
2018-05-22 13:33 ` Thomas Huth
2018-05-29 14:38 ` timsoft
2018-05-31 7:44 ` timsoft
2018-05-31 7:49 ` timsoft
2018-05-31 11:41 ` Thomas Huth
2018-05-31 11:42 ` Thomas Huth
2018-09-10 15:59 ` Jan Marti
2018-09-10 16:07 ` Jan Marti
2018-09-10 16:54 ` Jan Marti
2018-09-10 17:57 ` Jan Marti
2018-09-11 8:48 ` timsoft
2020-08-02 15:59 ` hakan
2021-02-12 10:51 ` Varun Chitre
2021-02-15 16:41 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150121211642.550.82493.malone@chaenomeles.canonical.com \
--to=prideaux90@hotmail.com \
--cc=1404278@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).