diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/674')
| -rw-r--r-- | results/classifier/zero-shot/108/other/674 | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/674 b/results/classifier/zero-shot/108/other/674 new file mode 100644 index 000000000..3018c0341 --- /dev/null +++ b/results/classifier/zero-shot/108/other/674 @@ -0,0 +1,29 @@ +graphic: 0.853 +device: 0.791 +boot: 0.712 +socket: 0.702 +PID: 0.672 +files: 0.663 +performance: 0.632 +KVM: 0.608 +debug: 0.604 +vnc: 0.598 +semantic: 0.596 +permissions: 0.536 +network: 0.486 +other: 0.271 + +Windows 7 fails with blue screen when KVM is enabled. +Description of problem: +The problem appeared immediately after a full system update of Arch Linux (The first for several months). Windows 7 images that had been running normally would fail with a blue screen and Error 0x7E immediately after displaying "Starting Windows". The same error would occur with a Windows 7 installation image, as in the command line above. When the "-enable-kvm" option was removed Windows would run normally but slowly. An old Clonezilla image booted without apparent problems. + +The final line on the blue screen reads: +*** STOP: 0x0000007E (0xC0000005,0x8BA3CA36,0x85186AA0,0x85186680) + +After getting the problem with the Arch package I cloned the source and built the latest version, getting the same error. However, when I build version 5.2.95 (v6.0.0-rc5-dirty) I found that this would run my existing Windows images (qcow2) and the installation ISO image. +Steps to reproduce: +1. +2. +3. +Additional information: + |