diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:07 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:17 +0200 |
| commit | 9260319e7411ff8281700a532caa436f40120ec4 (patch) | |
| tree | 2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_i386/host_missing/accel_missing/2420 | |
| parent | 225caa38269323af1bfc2daadff5ec8bd930747f (diff) | |
| download | qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip | |
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues_text/target_i386/host_missing/accel_missing/2420')
| -rw-r--r-- | gitlab/issues_text/target_i386/host_missing/accel_missing/2420 | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_i386/host_missing/accel_missing/2420 b/gitlab/issues_text/target_i386/host_missing/accel_missing/2420 new file mode 100644 index 000000000..0bf284e09 --- /dev/null +++ b/gitlab/issues_text/target_i386/host_missing/accel_missing/2420 @@ -0,0 +1,44 @@ +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> +``` |