yawgpp (Yet Another Windows Guest Performance Post)

In order to get VBS works it requires to have nested virt enabled. In this case the idle cpu usage is about 12 %(otherwise about 2%). Also I had to double the CPU count to get somehow "normal" performance.

I do not think we can do much, unless kernel/qemu gets patched. I guess that is the first set of patches: https://lwn.net/Articles/1051782/
I have seen another set of patches, but I cannot find it now.

More info here: https://forum.proxmox.com/threads/win-server-2k25-qemu-disk-ultra-slow.176153/page-2#post-818302

Maybe a good idea would be to ask Proxmox developers and @JonKohler if they have any idea if those patches will get integrated into the kernel.
 
I put together some manual how to run microsoft openvmm on proxmox :

https://github.com/bitranox/proxmox_openvmm

openvmm provides hyper-v devices on top of kvm (instead of qemu).

That should make it possible to run windows without VIRTIO Drivers - Windows should work with the underlying hyper-v devices on top of proxmox/kvm/openvmm, utilizing the hyper-v devices directly.

I only tested Alpine Linux VM on top of that stack until now, but I am hoping to run my hyper-v guests on the linux-vm and/or get also windows working.