add 18th iteration of classifier

1 files changed, 44 insertions, 0 deletions

diff --git a/results/classifier/118/graphic/674 b/results/classifier/118/graphic/674
new file mode 100644
index 000000000..297d1fbce
--- /dev/null
+++ b/results/classifier/118/graphic/674
@@ -0,0 +1,44 @@
+graphic: 0.853
+device: 0.791
+kernel: 0.763
+architecture: 0.716
+boot: 0.712
+socket: 0.702
+PID: 0.672
+files: 0.663
+mistranslation: 0.648
+arm: 0.642
+hypervisor: 0.635
+performance: 0.632
+risc-v: 0.624
+register: 0.610
+KVM: 0.608
+debug: 0.604
+vnc: 0.598
+semantic: 0.596
+virtual: 0.591
+VMM: 0.581
+permissions: 0.536
+network: 0.486
+TCG: 0.469
+ppc: 0.441
+x86: 0.435
+i386: 0.426
+user-level: 0.415
+assembly: 0.355
+peripherals: 0.353
+
+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:
+