diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 14:51:13 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 14:51:13 +0000 |
| commit | 225caa38269323af1bfc2daadff5ec8bd930747f (patch) | |
| tree | e0a5fefde9ee100ba6f32fb36de6707490e4164e /mailinglist/output_launchpad/1355644 | |
| parent | 904141bfb8d5385b75eb3b7afec1dcda89af65a7 (diff) | |
| download | emulator-bug-study-225caa38269323af1bfc2daadff5ec8bd930747f.tar.gz emulator-bug-study-225caa38269323af1bfc2daadff5ec8bd930747f.zip | |
add mailinglist scraper results
Diffstat (limited to 'mailinglist/output_launchpad/1355644')
| -rw-r--r-- | mailinglist/output_launchpad/1355644 | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/mailinglist/output_launchpad/1355644 b/mailinglist/output_launchpad/1355644 new file mode 100644 index 00000000..f51af9c8 --- /dev/null +++ b/mailinglist/output_launchpad/1355644 @@ -0,0 +1,22 @@ +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.] + |