add 18th iteration of classifier

1 files changed, 72 insertions, 0 deletions

diff --git a/results/classifier/118/performance/1031 b/results/classifier/118/performance/1031
new file mode 100644
index 000000000..81f703000
--- /dev/null
+++ b/results/classifier/118/performance/1031
@@ -0,0 +1,72 @@
+performance: 0.955
+hypervisor: 0.877
+socket: 0.864
+architecture: 0.856
+boot: 0.819
+device: 0.790
+kernel: 0.750
+ppc: 0.749
+PID: 0.740
+graphic: 0.666
+user-level: 0.640
+arm: 0.629
+x86: 0.616
+virtual: 0.613
+semantic: 0.601
+register: 0.567
+debug: 0.480
+TCG: 0.411
+VMM: 0.404
+vnc: 0.394
+files: 0.362
+permissions: 0.301
+risc-v: 0.276
+network: 0.274
+mistranslation: 0.203
+peripherals: 0.170
+assembly: 0.152
+i386: 0.036
+KVM: 0.026
+
+Intel 12th Gen CPU not working with QEMU Hyper-V nested virtualization
+Description of problem:
+When booting with Hyper-V + host-passthrough it gets stuck at tianocore, does not change until I reboot which then loops into windows diagnostics which leads nowhere. Done using Windows 10, tried using newest windows version and 1909.
+
+Specs: Manjaro Gnome 5.15 LTS, i5-12600k, z690 gigabyte aorus elite ddr4, rtx 3070ti.
+
+I’ve spent days trying to figure out what was messing with it and it turned out I could boot when messing with my CPU topology, for some reason my 12th gen + Hyper-V + host-passthrough only works with sockets. Cores and threads above 1 causes boot problems, apart from disabling vme which boots, but the hypervisor does not load.
+
+This fails (normal host-passthrough):
+```
+  <cpu mode="host-passthrough" check="none" migratable="on">
+    <topology sockets="1" dies="1" cores="6" threads="2"/>
+  </cpu>
+```
+
+This boots (-can only change sockets):
+```
+  <cpu mode="host-passthrough" check="none" migratable="on">
+    <topology sockets="12" dies="1" cores="1" threads="1"/>
+  </cpu>
+```
+
+This boots (-no hypervisor):
+```
+<cpu mode="host-passthrough" check="partial" migratable="off">
+    <topology sockets="1" dies="1" cores="6" threads="2"/>
+    <feature policy="disable" name="vme"/>
+  </cpu>
+```
+
+No matter what adjustment I do I cannot change the cores or threads or it will result in a boot failure, host-model just does not work once I boot the machine the host model changes to cooperlake.
+
+My current way of bypassing this is I’ve downloaded the QEMU source code, gone through cpu.c and modified the default skylake-client CPU model to match my CPU, then I added in most of my i5-12600k flags manually, this seems to work with a 35-45% performance drop in CPU and in ram. Without Hyper-V enabled and using the normal host-passthrough I get near bare metal performance.
+
+Tried with multiple versions of QEMU, EDK2, and loads of kernel versions (to add to this my i5-12600k gen does not work on kernel version 5.13 and below) even went ahead to try Ubuntu and had the same problem, my other (i7-9700k) PC works fine with Hyper-V. Also disabled my E-cores through bios resulting in the same issue. CPU pinning the P-cores to the guest does not seem to help.
+Steps to reproduce:
+1. Enable hyper-v in windows features
+2. Restart guest
+3. Boot failure
+Additional information:
+Hyper-V host-passthrough XML:
+https://pst.klgrth.io/paste/yc5wk