Nested Virtualization Unsupported – 3 Fixes for Hyper-V and VMware

1. Your Host CPU Doesn't Support Nested Virtualization

This is the most common reason. Nested virtualization means running a VM inside another VM. Your physical CPU needs Intel VT-x or AMD-V, and the feature must be turned on in the BIOS. I've seen dozens of cases where people have a modern CPU but the BIOS has virtualization disabled. That's the first thing to check.

Here's how to confirm if your CPU supports it:

1. Open Task Manager (right-click the taskbar, choose Task Manager).
2. Go to the Performance tab. Click CPU on the left.
3. Look at the bottom right under Virtualization. It will say Enabled or Disabled.

If it says Disabled, you need to go into your BIOS/UEFI settings to turn it on.

How to Enable Virtualization in BIOS

1. Restart your computer. As it boots, press the key to enter setup. Common keys: F2, Del, F10, Esc. Watch the screen – it usually says "Press F2 for Setup".
2. Inside BIOS, look for a setting called Intel Virtualization Technology, VT-x, AMD-V, or SVM Mode. It's often under Advanced or CPU Configuration.
3. Set it to Enabled.
4. Press F10 to save and exit. Your computer will restart.

After restart, open Task Manager again. Virtualization should now say Enabled. Try running your nested VM again. About 60% of the time, this fixes the problem.

Real-world scenario: A user on Windows 10 Pro with an i7-8700 tried to run a Hyper-V VM inside VMware Workstation 16. The error popped up. CPU checked out fine but BIOS had VT-x disabled. After enabling it, nested VM booted without issues.

2. Hyper-V Role Not Installed or Misconfigured on the Host

If your CPU supports virtualization and it's enabled in BIOS, the next suspect is Hyper-V itself. Nested virtualization in Hyper-V (the Microsoft version) needs the Hyper-V role installed on the host machine – not just inside the VM. I've seen people skip this step because they think the VM guest handles it.

Also, if you're using VMware Workstation or VirtualBox as your host, and you want to run a Hyper-V VM inside that, you need to enable a special setting in the hypervisor.

Fix for Hyper-V Host (Windows Server or Windows 10/11 Pro)

1. Open Control Panel → Programs and Features → Turn Windows features on or off.
2. Check the box for Hyper-V. Make sure both Hyper-V Management Tools and Hyper-V Platform are selected.
3. Click OK. Windows will install the feature. You'll need to restart.
4. After restart, open Hyper-V Manager. Right-click your VM and go to Settings.
5. Under Processor, find Compatibility. Check the box that says Enable nested virtualization (or something like that). On newer versions it's labeled Expose virtualization extensions to the guest OS.

After you apply, start the VM. The nested VM inside should now work. If you still get the error, run this PowerShell command as Administrator on the host:

Set-VMProcessor -VMName "YourVMName" -ExposeVirtualizationExtensions $true

Replace YourVMName with the actual name of your VM. This forces the setting on.

Fix for VMware Workstation Host

1. Shut down your guest VM.
2. Open VMware Workstation. Right-click your VM and choose Settings.
3. Go to Processors. Check the box Virtualize Intel VT-x/EPT or AMD-V/RVI.
4. Click OK. Start the VM.

That box tells VMware to pass the CPU virtualization features into the guest. Without it, the guest can't create its own VMs. I've fixed a dozen tickets just by checking that box.

3. Guest OS Doesn't Support Nested Virtualization

This one catches people off guard. Not every operating system inside a VM can run nested VMs. For example, Windows 10 Home doesn't have Hyper-V built in – you need Pro or Enterprise. Also, some Linux guest kernels need special modules loaded.

Here's what to check:

• Windows guest: Must be Windows 10/11 Pro, Enterprise, or Education. Also, the Hyper-V role must be installed inside the guest (just like on the host).
• Linux guest: You need kvm and kvm_intel or kvm_amd modules loaded. Run lsmod | grep kvm to see if they're loaded. If not, you might need to install the qemu-kvm package and reboot.
• macOS guest: Very limited. Only certain versions of macOS Server support nested virtualization, and only on Apple hardware.

Real-world scenario: A technician tried to run a nested Hyper-V VM on a Windows 10 Home guest. The host was fine, BIOS was fine, but the guest OS just didn't have the feature. Upgrading to Windows 10 Pro fixed it.

Quick-Reference Summary Table