To be honest the only thing which wonders me is, why some people have downplayed the issue when many others showed enough evidence. And that includes also Proxmox stuff. If you do not know what I mean, read the whole thread.
It happened because of the usual fanboyism and the fact that a lot of Proxmox users are running homelabs, not production-grade enterprise setups that need to work across multiple continents. Those of us who actually make our living doing this work and have to produce results knew by page 3 of this thread that this was a serious problem.
It doesn't matter what the metrics said - the VMs
felt slow to end users, and that's all that matters. Well-tuned virtualized infrastructure feels exactly like bare metal, and anyone who says otherwise doesn't know what they're doing.
For the people who were dismissing us, their node / nodes / clusters probably sit 50% idle all the time or more. However, like I said to one of these yahoos back in March, I live in the real world. My clients live in the real world. I can't tell them, "Well, Proxmox developers are waiting on the QEMU team to get their shit together and develop a fix, so we just have to sit tight and probably December 2026 to March 2027, it'll be all smoothed out."
The amount of people here who have a strong understanding of enterprise virtualization density, socket thermals, and core C-states is less than I think both you and I imagine. I can understand and appreciate the predicament the Proxmox development team is in - they have to wait for someone else to fix things so they can integrate those fixes into their product. Annoying. Been there. However, that's not an answer my clients will accept.
For most of my clients that have highly mixed VM configurations, we've switched them to Hyper-V on Windows Server 2025 Core for all Windows VMs on their newer hardware and for all their Linux / BSD VMs, we keep them running PVE 9.2 on older hardware. I sincerely hope the fix from the QEMU team comes soon though, I would much rather recommend PVE to clients, and will do so in the future once performance is at parity - or close enough to it - with Hyper-V / ESXi.
