restructure results

1 files changed, 46 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/105/network/485250 b/results/classifier/zero-shot/105/network/485250
new file mode 100644
index 00000000..635662a9
--- /dev/null
+++ b/results/classifier/zero-shot/105/network/485250
@@ -0,0 +1,46 @@
+network: 0.966
+mistranslation: 0.966
+semantic: 0.944
+device: 0.935
+instruction: 0.915
+boot: 0.907
+graphic: 0.904
+other: 0.891
+vnc: 0.865
+socket: 0.825
+KVM: 0.655
+assembly: 0.634
+
+nic e1000 network interface does not work with 32-bit windows 2003r2 with  sp2
+
+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
+
+Maybe you can try the e1000 drivers from Intel's site. You could also try using the stadard Qemu mac prefix of 52:54 (the first bit of the mac has a special meaning).
+
+I can reproduce this in qemu-kvm 0.12.50.
+
+Most likely a problem with the e1000 driver in QEMU. Funny thing is the guest seems to be able to obtain it's IP address via DHCP, then stops communicating.
+
+
+Can you still reproduce this issue with the latest version of QEMU?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+