summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/111/review/485258
blob: 253ee23261ae7cd94a238d22f74be76362fc72e2 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
device: 0.142
semantic: 0.120
vnc: 0.116
network: 0.092
other: 0.087
boot: 0.072
PID: 0.072
permissions: 0.066
files: 0.063
graphic: 0.048
performance: 0.037
socket: 0.033
debug: 0.032
KVM: 0.019
network: 0.255
debug: 0.207
PID: 0.169
performance: 0.075
vnc: 0.072
KVM: 0.036
other: 0.036
files: 0.034
device: 0.031
socket: 0.026
boot: 0.018
semantic: 0.015
graphic: 0.015
permissions: 0.010

64-bit win2003r2 with sp2 64-bit with network type rtl8139 generates blue screen after running network test

64-bit win2003r2 with sp2 64-bit with network type rtl8139 generates blue screen after running network test

Steps to recreate:
1) install qemu frm git clone git://git.savannah.nongnu.org/qemu.git

2)Download Soap Stone Benchmark(http://soap-stone.sourceforge.net/) and IBM java 1.4 for windows

3)use  win2k3r2sp2 64-bit as the server and win2k3r2sp2 32-bit as client (this bug does not occur when win2k3r2sp2 64-bit is the client)

4) Running the test will reset the  network interface on the server(win2k3r2sp264bit).

5)Then shutdown the server(win2k3r2sp2 64bit), which will generate a blue screen.


Qemu cmd line used:
/usr/local/bin/qemu-system-x86_e 'vm1'  -drive file=win2003r2-64.raw,boot=on -net nic,vlan=0,macaddr=20:20:20:00:00:01,model=rtl8139  -net tap,vlan=0,script=/home/yogi/qemu-ifup  -m 10240   -usbdevice tablet -vnc :0 -enable-kvm

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

I have attached the generated Blue Screen..

Thx
yogi



Can you still reproduce this problem with the latest version of QEMU?

[Expired for QEMU because there has been no activity for 60 days.]