From: Joel Schopp <joel.schopp@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 485250] Re: nic e1000 network interface does not work with 32-bit windows 2003r2 with sp2
Date: Wed, 02 Jun 2010 16:46:10 -0000 [thread overview]
Message-ID: <20100602164611.23341.8783.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 20091119103034.30387.95497.malonedeb@wampee.canonical.com
** Tags added: windows
--
nic e1000 network interface does not work with 32-bit windows 2003r2 with sp2
https://bugs.launchpad.net/bugs/485250
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Bug description:
nic e1000 network interface does not work with win2k3r2 32bit
e1000 driver in win2k3r2 32bit seems to be broken. The interface is able to
receive ip from the dhcp server, but not able to ping it from any linux guest or
host, but was able to ping it from windows guest.
Running network test, netperf, between the windows guest fails with the message
"netperf: receive_response: no response received. errno 104 counter 0"
cmdline used:
/usr/local/bin/qemu-system-x86_64 -drive file=win2003r2sp2-32.raw,boot=on -net nic,vlan=0,macaddr=20:20:20:00:00:04,model=e1000 -net tap,vlan=0,script=/home/yogi/qemu-ifup -m 2048 -enable-kvm -usbdevice tablet -vnc :1
uname -a
Linux bc1cn9 2.6.30.9-96.fc11.x86_64 #1 SMP Wed Nov 4 00:02:04 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
Distro: fedora 11
Thx
yogi
next parent reply other threads:[~2010-06-02 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091119103034.30387.95497.malonedeb@wampee.canonical.com>
2010-06-02 16:46 ` Joel Schopp [this message]
2010-06-02 20:16 ` [Qemu-devel] [Bug 485250] Re: nic e1000 network interface does not work with 32-bit windows 2003r2 with sp2 Iggy
2010-06-24 6:49 ` Jes Sorensen
2016-11-07 18:21 ` Thomas Huth
2017-01-07 4:17 ` Launchpad Bug Tracker
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=20100602164611.23341.8783.launchpad@soybean.canonical.com \
--to=joel.schopp@gmail.com \
--cc=485250@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).