1 files changed, 43 insertions, 0 deletions
diff --git a/results/classifier/118/performance/1677 b/results/classifier/118/performance/1677
new file mode 100644
index 00000000..2b757d89
--- /dev/null
+++ b/results/classifier/118/performance/1677
@@ -0,0 +1,43 @@
+performance: 0.972
+graphic: 0.892
+x86: 0.879
+boot: 0.868
+device: 0.839
+semantic: 0.743
+risc-v: 0.736
+socket: 0.706
+ppc: 0.680
+files: 0.678
+vnc: 0.658
+PID: 0.639
+architecture: 0.635
+kernel: 0.615
+debug: 0.603
+hypervisor: 0.568
+VMM: 0.534
+arm: 0.447
+register: 0.422
+permissions: 0.406
+i386: 0.403
+mistranslation: 0.373
+peripherals: 0.348
+user-level: 0.348
+virtual: 0.341
+network: 0.309
+TCG: 0.296
+assembly: 0.269
+KVM: 0.193
+
+qemu-system-x86_64 cannot run on Windows when -smp is specified with a value higher than `1`. An important argument for any expectation of VM performance
+Description of problem:
+qemu-system-x86_64 seems to crash on Windows the moment you try to use -smp to define more vcpus, even the basic usage of `-smp 4` will cause qemu to segfault after the guest's boot option is selected.
+Steps to reproduce:
+1. `qemu-system-x86_64 -smp 4 -cdrom rhel-9.2-x86_64-dvd.iso -drive if=pflash,format=raw,unit=0,readonly=on,file=edk2-x64/OVMF_CODE.fd -m 6G -nodefaults -serial mon:stdio`
+2. Select the boot option to begin your installation
+3. qemu hangs for 10 or so seconds then throws a Segmentation Fault.
+Additional information:
+1. This does not happen if -smp arguments are omitted, but running VMs with a single vcpu thread is slow and painful.
+2. This still happens even without OVMF (Traditional bios booting)
+3. This still happens even without -defaults and without a serial device
+
+Only output from qemu at death is `Segmentation fault`