Here is a follow-up on my initial post. I was running out of ideas, so I've decided to let Claude code SSH connect to my production host (because why not?). Figured it might be able to shed some new light on the issue.
Turns out it really did...
An interesting thread.
I came here exploring reasons why Windows VMs always use 2-3 % of CPU doing apparently nothing.
My Windows Server 2025 was already in the same ballpark as Windows Server 2022 and 2016 VMs - I didn't get 10% CPU usage as...
@fiona Thanks for that - I see pve-qemu-kvm-10.2.1-2 in pve-test as of time of writing.
I had 2 updates on my test lab whether or not the other one is applicable to this bug or just coincidence wouldn't know.
For those that used workaround from...
@martin_comp Yes, the issue affects IO delay (the name for iowait in the UI) too.
A fix was applied in git master and the new pve-qemu-kvm=10.2.1-2 package is currently going through internal testing.
Well... not so much freezing but I have something - non-issue I am proper pushing that box to its limits, its only a dev box. There is no bug or no reason why other than I have, purposely, crammed that box full. This is not on Debian, Proxmox or...
I don’t see any problem with packages that have already been flagged as problematic remaining in the “test repository.”
If that issue hadn’t been present in the test repository, we wouldn’t have noticed it or reported it in the first place.
I...
With respect, disagree - yes there is an issue but seemingly cosmetic. There is a suggestion that if you dont enable iothreads then you're not even affected. Discussed elsewhere - its "test" repo for a reason.
Yes there's that issue but early...
Running great on test lab, small cluster of Dell 7070.
CPU(s) - 8 x Intel(R) Core(TM) i7-9700T CPU @ 2.00GHz (1 Socket)
Kernel Version - Linux 7.0.0-1-rc6-pve (2026-03-30T09:17Z)
Boot Mode- EFI (Secure Boot)
Manager Version -...
From the analysis until now, the IO pressure seems to be a cosmetic issue or rather accounting issue in the kernel. QEMU switched to using io_uring for event loops with QEMU 10.2. The issue appears in combination with IO threads, where a blocking...
@djsami thats why you dont use the test repository in production.
as the name implies it is a repository for testing things. its bleeding edge stuff.
if you need things to just work, use the enterprise repository, where only well tested releases...
its like using debian sid and then complaining about issues with it.
according to his logic debian sid should be qc-tested since the repository is available to thousands.
thats not how it works.
test = bleeding edge stuff with a decent chance...
Those expectations arise precisely because you’ve actually used it and experienced its shortcomings firsthand.
I understand your concerns, but ultimately, the use of the test repository is at your own risk.
i repeat, dont use the test-repo for production.
developers state its only for testing-purposes and not for production-use as evidenced by my screenshot from their own wiki.
you ignoring this is purely on you and on noone else.
you could have run...
Sorry, I'm out. All of the above is on you. Who told you to implement the "test" repository in "an enterprise-grade environment of this scale".
It is not published in either pve-no-subscription or pve-enterprise repositories.
I don't dispute...
Inneresting! I did not have that occur on mine.
For sure the proxmox team will identify the reason why - lets remember this is a package published to test so those of us brave enough to use that will know the caveats. I reckon you might want to...