I was searching for days in order to get my WIndows 10 Pro Desktop VM back online again (while keeping the host cpu) after enabling Core Isolation (aka Virtualization-based Security) without doing a snapshot in advance. And then I luckily found this link. It turned out that getting the nested Hyper-V and WSL running on my Intel i7-13700T Proxmox VE 8.1 host was just a matter of adding
Code:
args: -cpu host,level=30
in the VM config file.
Afterwards the VM instantly booted again but still felt a bit slow and caused its assigned vcpus to constantly run at high load. After carefully...
I may have come across what you're probably after in my own feverish research, and couldn't help but make an account to link it ^^ @AllanM
