qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: hakan <1404278@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1404278] Re: tap connections not working on windows host
Date: Sun, 02 Aug 2020 15:59:04 -0000	[thread overview]
Message-ID: <159638394450.11064.9327137954898121885.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20141219153639.25009.84583.malonedeb@wampee.canonical.com

Hi,

I want to run u-boot for x86_64 architecture in windows10 and I am using
qemu-5.0.0, the latest version of qemu. The TAP adapter for Linux (host)
worked successfully and I communicated between u-boot (guest) and Linux
(host), but the result for Windows (host) failed.

I installed the Tap Network Adapter for windows and renamed it to "tap0" . when I ran the qemu with the following command without creating a bridge, u-boot was successfully initialized, but I cannot ping Windows (host).
qemu-system-x86_64.exe -bios u-boot.rom -nographic -device  e1000,netdev=mynet0 -netdev tap,id=mynet0,ifname=tap0

When I check (right click> status) for Tap0 it says No Network Connection.
I terminated qemu and connected tap0 to the internet using the config files I downloaded for OpenVPN.
When I checked tap0 again, I saw "Ipv4: Internet" but when I try to run qemu this way, I get an error like this.

tap: Could not open 'tap0'
qemu-system-x86_64.exe: Device 'tap' could not be initialized

-- 
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


  parent reply	other threads:[~2020-08-02 16:11 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
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 [this message]
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=159638394450.11064.9327137954898121885.malone@chaenomeles.canonical.com \
    --to=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).