1 files changed, 74 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/2420 b/results/classifier/118/graphic/2420
new file mode 100644
index 000000000..2773b7fb6
--- /dev/null
+++ b/results/classifier/118/graphic/2420
@@ -0,0 +1,74 @@
+graphic: 0.966
+virtual: 0.890
+performance: 0.868
+hypervisor: 0.783
+architecture: 0.759
+socket: 0.710
+device: 0.661
+ppc: 0.657
+user-level: 0.627
+mistranslation: 0.562
+arm: 0.546
+vnc: 0.540
+debug: 0.530
+semantic: 0.524
+boot: 0.499
+kernel: 0.497
+peripherals: 0.481
+VMM: 0.450
+x86: 0.428
+PID: 0.416
+network: 0.397
+risc-v: 0.353
+TCG: 0.332
+permissions: 0.302
+i386: 0.280
+KVM: 0.271
+assembly: 0.226
+register: 0.148
+files: 0.100
+
+Error: Deprecated CPU topology (considered invalid): Unsupported cluster parameter musn't be specified as 1
+Description of problem:
+warning: Deprecated CPU topology (considered invalid): Unsupported clusters parameter mustn't be specified as 1
+VM does not start
+
+What I've tried so far to fix:
+
+- Removed the offending `clusters="1"` parameter in the XML, both via virsh edit and virt-manager but the sucker comes back every time!
+
+- Creating a completely new VM from scratch, just keeping the qcow2 for Windows. What happens then is funny: The initial setup goes well. Machine type automatically gets set to q35 version 9.0. After setting up my cores (pinning) for the VM (7C/14T for the VM 1C/2T for host), there is no "clusters" parameter anymore. So the first start went well. After a RESTART of the whole host machine and subsequent launch of the VM guess what happened? The "clusters" thing is back in full swing.
+Steps to reproduce:
+1. Create Windows 11 VM with virt-manager
+2. Try to do core pinning and setting up the following in virt manager before
+- Copy CPU configuration from host (host-passthrough)
+- Manually set CPU structure via GUI to 1 Socket, 7 Cores, 2 Threads on an 8 Core (in my case 11900k)
+3. Observe result in XML being: 
+ `<topology sockets="1" dies="1" clusters="1" cores="7" threads="2"/>`
+
+Again, the "clusters" entry leads to the VM not starting. Removing it doesn't work, it comes back straight away. I tried in virt-manager as well as with virsh edit.
+Additional information:
+My core pinning for reference:
+
+```
+<vcpu placement="static">14</vcpu>
+  <iothreads>1</iothreads>
+  <cputune>
+    <vcpupin vcpu="0" cpuset="0"/>
+    <vcpupin vcpu="1" cpuset="8"/>
+    <vcpupin vcpu="2" cpuset="1"/>
+    <vcpupin vcpu="3" cpuset="9"/>
+    <vcpupin vcpu="4" cpuset="2"/>
+    <vcpupin vcpu="5" cpuset="10"/>
+    <vcpupin vcpu="6" cpuset="3"/>
+    <vcpupin vcpu="7" cpuset="11"/>
+    <vcpupin vcpu="8" cpuset="4"/>
+    <vcpupin vcpu="9" cpuset="12"/>
+    <vcpupin vcpu="10" cpuset="5"/>
+    <vcpupin vcpu="11" cpuset="13"/>
+    <vcpupin vcpu="12" cpuset="6"/>
+    <vcpupin vcpu="13" cpuset="14"/>
+    <emulatorpin cpuset="7,15"/>
+    <iothreadpin iothread="1" cpuset="7,15"/>
+  </cputune>
+```