https://docs.microsoft.com/en-us/virtua … ualization
Some more reading suggests WS 2016 is the first to support nested hyper-V on intel processors, while you need WS 2019 to use hyper-V nesting on amd procesoors.
Running Hyper-V on kvm appears to be completely unsupported.
If the host has multiple processors, you could maybe passthrough a full processor to the windows server VM .
I checked it out and on both server 2016 and 2019 it works. Thanks!
]]>Some more reading suggests WS 2016 is the first to support nested hyper-V on intel processors, while you need WS 2019 to use hyper-V nesting on amd procesoors.
Running Hyper-V on kvm appears to be completely unsupported.
If the host has multiple processors, you could maybe passthrough a full processor to the windows server VM .
]]>systool -m kvm_amd -v | grep nested
nested = "1"
And I run qemu with -enable-kvm -cpu host
qemu-system-x86_64 -m 4096 -hda winsys2012r2.img -enable-kvm -cpu host
Everything as arch wiki shows
]]>