summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/hypervisor/1355644
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1355644')
-rw-r--r--results/classifier/deepseek-2-tmp/output/hypervisor/135564418
1 files changed, 18 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1355644 b/results/classifier/deepseek-2-tmp/output/hypervisor/1355644
new file mode 100644
index 00000000..89d7cc6d
--- /dev/null
+++ b/results/classifier/deepseek-2-tmp/output/hypervisor/1355644
@@ -0,0 +1,18 @@
+
+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.
\ No newline at end of file