[GH-ISSUE #89] Defaults for Windows VMs #64

New issue

Open

opened 2026-03-02 15:47:40 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 15:47:40 +03:00

Owner

Originally created by @proxforge on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/89

Originally assigned to: @mkellermann97 on GitHub.

When creating a VM in PegaProx, User should maybe be warned about using host-cpu profile as performance drops very hard because of features windows enables, when host cpu profile is used. windows enables things like credential guard, vbs etc. which is kinda based on hyper-v which is then used inside your windows vm running already on kvm.

https://forum.proxmox.com/threads/the-reasons-for-poor-performance-of-windows-when-the-cpu-type-is-host.163114/

Originally created by @proxforge on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/89 Originally assigned to: @mkellermann97 on GitHub. When creating a VM in PegaProx, User should maybe be warned about using host-cpu profile as performance drops very hard because of features windows enables, when host cpu profile is used. windows enables things like credential guard, vbs etc. which is kinda based on hyper-v which is then used inside your windows vm running already on kvm. https://forum.proxmox.com/threads/the-reasons-for-poor-performance-of-windows-when-the-cpu-type-is-host.163114/

kerem commented

2026-03-02 15:47:40 +03:00

Author

Owner

@gyptazy commented on GitHub (Feb 27, 2026):

Hey @proxforge,

Thanks for reporting this and I think this is a special corner case where

It’s not a bug in PegaProx
Only affects Windows systems
This hopefully should soon be solved by upstream

There’re already some rough ideas how to fix and solve it, they’re not the best and just POCs of showcasing the potential fixes like: https://cdn.gyptazy.com/proxmox/patches/fix_windows2025_server_vbs_high_cpu_load/

In the end, I don’t think this should be part of PegaProx, but happy to hear more opinion on that.

Cheers,
gyptazy

@gyptazy commented on GitHub (Feb 27, 2026): Hey @proxforge, Thanks for reporting this and I think this is a special corner case where - It’s not a bug in PegaProx - Only affects Windows systems - This hopefully should soon be solved by upstream There’re already some rough ideas how to fix and solve it, they’re not the best and just POCs of showcasing the potential fixes like: https://cdn.gyptazy.com/proxmox/patches/fix_windows2025_server_vbs_high_cpu_load/ In the end, I don’t think this should be part of PegaProx, but happy to hear more opinion on that. Cheers, gyptazy