windows 10 hyper v vs virtualbox performance

Since I rarely use Hyper-V, it's not a big issue, but it would be nice if I could do so without having to reboot. Disabling Hyper-V features allowed me to run them as before. On Friday, after a reboot Thursday night, I could run older VMs, but neither of the VMs I had recently created would start: I got the error mentioned previously. I was still able to run all VMs without problem. Last Thursday, I installed 15.5.6, but did not reboot. I created two new VMs, which were linked clones of an existing VM (Windows Server 2019) and had no problems with them that day.

At that time, I had no problems running VMs. The chain of events, as I remember it, was that after installing 15.5.5, I enabled the Hyper-V features and rebooted. We're working with MS to address the use-case, but we don't have a solid delivery date to communicate just yet. Our stack is obviously more mature, so when using the Hyper-V API's we had to make some compromises.

We actually test ESXi in Workstation (for linux) VMs in monster CI pipelines. The reason that nested virtualization doesn't work is because our virtual machine monitor ('vmm', the 'hypervisor' part of the hypervisor) code was designed and optimized to do this, but Hyper-V monitor code is not. We have a KB but, NGL, it's complete trash and I'm having it rewritten.

Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.

On the host operating system, click S tart > Run, type gpedit.msc, and click Ok.

Disable the group policy setting that was used to enable Credential Guard.

To disable Device Guard or Credential Guard the first step is the following:

Windows 10 hyper v vs virtualbox performance