This incompatibility is caused by Hyper-V because virtualization extensions are not exposed to type 2 hypervisors installed on a Windows machine where the Hyper-V role is enabled. Only one software component can use Intel VT-x or AMD-V at a time. These virtualization extensions are not available for VMware Workstation and VirtualBox when Windows loads. Hyper-V takes control of virtualization extensions when Windows boots. All hypervisors require processor virtualization extensions, which are instruction sets for hardware virtualization – Intel VT-x or AMD-V.

A type 1 hypervisor is installed on top of hardware.

A type 2 hypervisor is installed on the operating system that is running on hardware. VMware Workstation, VMware Player, and VirtualBox are type 2 hypervisors, while Hyper-V is a type 1 hypervisor.

What causes this problem with Hyper-V? Let’s take a closer look. You can install VMware Workstation and VirtualBox, and run VMware VMs and VirtualBox VMs on the same computer, but not simultaneously. The errors occur even if Hyper-V VMs are not running at that time. Background and Working PrincipleĪfter you install VMware Workstation, VMware Player, or Oracle VirtualBox on a Windows machine, you might get errors when starting a VM in these virtualization applications. This blog post explains what causes these errors, how to fix them, and how to run other virtualization applications on a computer with Hyper-V. Errors that happen when you run VMs on non-Hyper-V virtualization applications cause significant problems. When you install a virtualization application on a Windows machine on which Hyper-V or related services are installed, errors can often occur. By Michael Bose Virtualization Applications Are Not Working: What Do You Do?

Vmware player