From: Thomas Huth <1196727@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1196727] Re: SLIRP on Windows 7 64-bit host or is it me?
Date: Thu, 20 Jul 2017 11:56:07 -0000 [thread overview]
Message-ID: <150055176790.24314.4415527643982016261.malone@soybean.canonical.com> (raw)
In-Reply-To: 20130701220319.19436.23553.malonedeb@chaenomeles.canonical.com
Triaging old bug tickets ... can you still reproduce this problem with
the latest version of QEMU (currently v2.9.0)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1196727
Title:
SLIRP on Windows 7 64-bit host or is it me?
Status in QEMU:
Incomplete
Bug description:
Version: 1.5.1 and tried latest in Git, compiled for x86_64 Windows 64-bit
Host: Windows 7 64-bit
Guest: FreeBSD 9.1 i386, RHEL 6.4 x86_64, SLES 11.2 x86_64, OpenSUSE 12.3 ppc64, Fedora 18 ppc64
libiconv: 1.14
glib: 2.28.8
gettext: 0.18.1.1
pixman: 0.30.0
libSDL: 1.2.14
Driver: virtio-net-pci
Emu: full (non-KVM)
I'm new to Windows 7 64-bit as a host for QEMU (previously I was
running QEMU on Windows XP with no issues) so it could be me, now on
Windows 7 SLIRP only works for me connecting internally from the host
to the guest via SLIRP redirect, but any outbound requests from the
guest to the Internet are failing with the following:
if_start...
m_get...
m = 61f7bd40
ip_input...
m = 61f7bd40
m_len = 48
tcp_input...
m = 61f7bd40 iphlen = 20 inso = 0
tcp_fconnect...
so = 33e140
connect()ing, addr.sin_port=80, addr.sin_addr.s_addr=206.190.36.45
tcp fconnect errno = 10035-Unknown error
icmp_error...
msrc = 61f7bd40
msrc_len = 48
10.0.2.5 to 206.190.36.45
m_get...
m = 61f7b6c0
ip_output...
so = 0
m0 = 61f7b6c0
if_output...
so = 0
ifm = 61f7b6c0
if_start...
arp_table_search...
ip = 0x502000a
found hw addr = 52:54:00:12:34:56
m_free...
m = 61f7b6c0
tcp_close...
tp = 377840
m_free...
m = 0
m_free...
m = 61f7bd40
Am I doing something wrong with my Windows host configuration or is
this a bug in SLIRP only on W64 and not W32?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1196727/+subscriptions
next prev parent reply other threads:[~2017-07-20 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 22:03 [Qemu-devel] [Bug 1196727] [NEW] SLIRP on Windows 7 64-bit host or is it me? Kenneth Salerno
2013-08-15 17:55 ` [Qemu-devel] [Bug 1196727] " Kenneth Salerno
2013-08-15 19:11 ` Stefan Weil
2017-07-20 11:56 ` Thomas Huth [this message]
2017-07-20 23:03 ` Kenneth Salerno
2017-07-21 8:27 ` Thomas Huth
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=150055176790.24314.4415527643982016261.malone@soybean.canonical.com \
--to=1196727@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.