I can confirm EnablePerCpuClockTickScheduling=2 fixes / works around the issue. CPU load returns to 23H2 levels and CPU cores assigned to the VM are able to enter deeper C states as expected. Thank you!
I've attached this info to the QEMU ticket...
Machine left for 2 hours idling, virtio-nic connected, WiFi turned off from action center in Windows, screen off, average residency:
Pkg%pc2 Pkg%pc3 Pkg%pc6 Pk%pc10 PkgWatt
4.77 0.00 71.89 0.00 2.63
4.77 0.00 71.89 0.00 2.63...
No, it's off. 24H2 indeed introduced per core clock ticks, and apparently that is what kills residency in VMs. I don't really understand why, but that is one difference in the KiSetTime/KiGetTime functions in 24H2 compared to Server 2022, for...
Something's wrong with this OS. You can bump that number in the Python script, I tested with 500ms. The pkg pc6 residency then reaches 60-70% when idle, as was the case with previous versions. Effects can be easily seen, for example, the cursor...
For completeness, here is also my full virsh XML for this VM:
<domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
<name>console</name>
<uuid>837730e7-258a-4357-865b-375fe422825f</uuid>
<memory...
Hi guys,
I spent a quite some time trying everything mentioned here and in other threads related to this. For me, the benchmark was being able to lower PkgWatt and reach Pkg%pc2 and Pkg%pc6 residency in my VM. This VM I run on my laptop...