summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1355644
blob: 01da55c9f3b6ae21caeb5631722f3413e0a729fb (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
graphic: 0.805
device: 0.544
semantic: 0.465
performance: 0.381
boot: 0.296
permissions: 0.268
other: 0.249
network: 0.246
socket: 0.235
debug: 0.229
PID: 0.212
vnc: 0.196
files: 0.180
KVM: 0.036

windows7 reboot bluesreen 0x0000005c

I have met sevaral blue screen with 0x0000005c(0x0000010b,0x00000003,0x00000000,0x00000000) after windows7 reboot.
It always happens just before the windows iron animation appears.

my qemu version is qemu-2.1.0
my guest os is windows7 32bits sp1

my qemu commandline is 
./x86_64-softmmu/qemu-system-x86_64 -m 2048 -hda system.inst -spice port=5940,disable-ticketing -monitor stdio --enable-kvm

This bug  doesn't happen always,and i don‘t know how to reproduce it.

But i have a special way to produce such a bluescreen.
I set nmi dump on and set windows to collect dump file and set auto reboot after system fail on. 
Then i send a nmi to guest, and then after collecting dump file , windows will auto reboot and then such a blue screen happens.
And this can be  reproduced always.

Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

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