Windows Server 2025 CPU suddenly at 100%

Huh? Didn't you go with a workaround because it wouldn't fix the problem?

Code: 
https://github.com/proxmox/qemu-server/commit/b69480d6110c005b9eb936c55c0438607d10975b

Well, even if this did fix 100% of the issues, enabling VBS would make the Start button on Windows unresponsive—it'd be completely useless. Shouldn't Proxmox just officially recommend disabling VBS at this point?

I don't think the issue that needs to be fixed is the one where it reaches 100%; rather, I think it's any problem that occurs when MBEC is used after VBS is enabled.

If anything, things are even worse now than they were on April 23, right?

Code: 
https://forum.proxmox.com/threads/high-vm-exit-and-host-cpu-usage-on-idle-with-windows-server-2025.163564/post-849774

It wasn't exactly ideal, but it was a lot better than it is now.
 
Last edited:
mariol said:
A fix available now: https://pve.proxmox.com/wiki/Roadmap#9.2-known-issues (Point 3) "On Intel hosts, Windows 11/2022/2025 VMs with host CPU type and VBS enabled may intermittently freeze"
Click to expand...
This isn't a conversation. (Though maybe you just don't want to talk to me.)
Enabling VBS doesn't cause CPU usage to reach 100%, but the Windows Start button stops responding, rendering it completely useless.

Is the Start menu a feature that isn't used in Windows?
 
You must log in or register to reply here.
Top Bottom
Back