claron-cloud-diagnostics-20260519-1647.zip Since updating to 7.3.0, when my VM is running either core 0 or 16 is pinned at 100% I have traced the issue to QEMU but cannot resolve. I have tried various settings in the VM config. This issue is not linked to the VM OS as the core is pinned at 100% before the OS VM boots. VM: Windows Server 2016 running Blue Iris/CCTV workload Initial symptom: One host CPU thread permanently pinned at ~100% qemu-system-x86 consuming up to ~220% host CPU Guest Windows CPU usage only ~9% Host overall remained mostly idle (~88% idle) VM configuration changes attemptedReduced VM from: 16 vCPUs (8c/16t) to 8 vCPUs (4c/8t) Applied explicit CPU pinning: VM vCPUs pinned to cores 1-4,17-20 Emulator/iothread pinned to 0,16 Added: <kvm><hint-dedicated state='on'/></kvm> Disabled Hyper-V enlightenments: removed entire <hyperv> block Disabled Windows dynamic tick: bcdedit /set disabledynamictick yes Set Windows power plan to High Performance Storage changes attemptedOriginal VM used SATA emulation: <target dev='hdc' bus='sata'/> Installed VirtIO drivers inside Windows Migrated all disks to VirtIO-SCSI Added: <controller type='scsi' model='virtio-scsi'> <driver queues='8'/> Retained: cache='none' io='native' Tested with: qcow2 system disk raw physical disk passthrough devices Network changes attemptedOriginal NIC config: type='direct' macvtap eth2 mode='bridge' Changed to: <interface type='bridge'> <source bridge='br0'/> virtio-net Graphics/device emulation changes attemptedRemoved: VNC graphics QXL video USB tablet watchdog VirtIO ISO/CD-ROM unused SATA/IDE devices