1 files changed, 48 insertions, 0 deletions
diff --git a/results/classifier/118/device/808 b/results/classifier/118/device/808
new file mode 100644
index 000000000..deb066b31
--- /dev/null
+++ b/results/classifier/118/device/808
@@ -0,0 +1,48 @@
+device: 0.963
+x86: 0.935
+graphic: 0.930
+architecture: 0.915
+boot: 0.898
+peripherals: 0.892
+KVM: 0.888
+hypervisor: 0.884
+virtual: 0.834
+ppc: 0.829
+semantic: 0.826
+performance: 0.818
+vnc: 0.796
+PID: 0.752
+VMM: 0.739
+files: 0.698
+network: 0.682
+risc-v: 0.670
+mistranslation: 0.662
+permissions: 0.658
+socket: 0.638
+kernel: 0.603
+TCG: 0.595
+register: 0.555
+arm: 0.554
+user-level: 0.522
+debug: 0.443
+assembly: 0.282
+i386: 0.194
+
+virtio-scsi in Windows guests cause QEMU to abort/crash
+Description of problem:
+* Attempting to load the virtio-scsi drivers in a Windows guest causes the VM to abort/crash.
+Steps to reproduce:
+* `qemu-system-x86_64 -accel kvm -m 4G -device virtio-scsi-pci,id=scsi0 -drive media=cdrom,file=windows7-x64.iso -drive media=cdrom,file=virtio-win-0.1.173.iso`
+ * Boot the installer ISO, click through all the menus to eventually get to Custom Install
+ * In "Where do you want to install" click Load driver
+ * Browse E: drive and pick the first amd64/w7 folder
+ * Should show "Red Had VirtIO SCSI pass-through controller"
+ * Click Next
+ * Abort/crash
+
+Same thing happens with VM's that used to work already running the virtio-scsi drivers. When they boot the VM aborts.
+Additional information:
+```
+qemu-system-x86_64: ../accel/kvm/kvm-all.c:1760: kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
+Aborted (core dumped)
+```