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...
Excellent! Thing is, as alluded to previously, I dont actually think its increased io. I'm not the worlds best at iotop but I wasnt seeing any difference - only in the realtime bar i/o delay and the io pressure stall graph.
Good luck hunting...
Interesting. Here is mine for comparison. No zfs on this box all lvmthin. can find one if more results desired.
Initial findings after reinstalling pve-qemu-kvm 10.2.1-1, uplift of all Windows VMs to pc-q35-10.2 and flipping aio=threads on all...
Thank you OP for testing and workaround!
Same experiences on lesser hardware, small cluster of Dell Optiplex 7070. Unfortunately for me it coincided with research on zswap implementation so spent time eliminating that as a symptom first.
For...
Further testing has confirmed that the issue recurs after applying this update…
Reinstalling the package with a specific version resolves the issue.
I wonder if they'll release a fix...
apt list --upgradable
libpve-common-perl/stable 9.1.9...
You know what? I did actually log a ticket with detailed information. Turns out there was a very old (2021, 2022?) ticket that had precisely one line it it, logged against version 7 with zero activity.
More up to date ticket closed as duplicate...