How To Enable Virtualization In Vmware Virtual Machine

To enable nested virtualization in a VMware virtual machine, you must configure the host system, the guest VM settings, and the guest operating system to support running a hypervisor inside a VM. This process, commonly searched as "enable nested virtualization vmware," resolves the "VT-x/EPT not supported" error and allows you to run WSL 2, Hyper-V, or another hypervisor within a VMware guest, though doing so can make it easier for software to hide virtual machine detection. This same concept of a software-based environment is fundamental to the Ethereum virtual machine, which executes smart contracts on a decentralized network.

Why enable nested virtualization in a VMware virtual machine?

Nested virtualization lets you run a hypervisor, such as Hyper-V, WSL 2, or another VMware or VirtualBox instance, inside an existing VMware virtual machine. This is essential for developers, IT professionals, and testers who need to build lab environments, test multi-tier architectures, or run container platforms like Docker Desktop with WSL 2 inside a VM. Without nested virtualization, attempting to start a hypervisor inside a guest VM produces the "VT-x/EPT is not supported on this platform" error, because the guest lacks access to the physical CPU's hardware virtualization extensions.

Prerequisites

Before you begin, confirm that your physical host meets these requirements:

• The host CPU must support hardware-assisted virtualization, Intel VT-x or AMD-V.
• Hardware-assisted virtualization must be enabled in the physical host's BIOS/UEFI settings (often labeled VT, VT-x, AMD-V, Vanderpool Technology, VMX, or Virtual Machine Extensions).
• You must be using VMware Workstation Pro or VMware ESXi. Nested virtualization is not available in VMware Workstation Player.
• On a Windows host, certain Windows features that also use virtualization can conflict with VMware Workstation's nested virtualization and must be disabled first.

Step 1: Disable conflicting Windows features on the host

On a Windows host, the following features and security settings can prevent VMware Workstation Pro from exposing hardware virtualization to a guest VM:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Virtualization-Based Security (VBS)
• Memory Integrity (also called Core Isolation)

To disable these:

1. Open the Windows Features dialog (search for "Turn Windows features on or off"). Uncheck Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform. Click OK.
2. Open Windows Security, go to Device Security > Core Isolation details, and turn off Memory Integrity.
3. If VBS remains active, you may need to disable it via Group Policy or a registry edit. Search for "disable virtualization-based security" for your Windows version.
4. Restart the host system for all changes to take effect.

Step 2: Enable hardware-assisted virtualization in BIOS or UEFI

Hardware-assisted virtualization must be enabled at the physical host's firmware level.

1. Restart the host computer. During the boot process, press the key to enter BIOS/UEFI setup, typically F2, F10, or Del.
2. Navigate to the Advanced, Processor, or CPU Configuration section. The exact menu name varies by manufacturer.
3. Locate the setting for Intel VT-x, AMD-V, or Vanderpool Technology. Set it to Enabled.
4. Save changes and exit the BIOS/UEFI interface. The system will reboot.

Step 3: Enable nested virtualization in the VMware virtual machine settings

For VMware Workstation Pro

1. Select the virtual machine in the library. Go to VM > Settings.
2. Click the Hardware tab, then select Processors.
3. Check the box labeled "Virtualize Intel VT-x/EPT or AMD-V/RVI."
4. Click OK to save the settings.

For VMware ESXi

1. Right-click the virtual machine in the inventory and select Edit Settings.
2. Go to the Virtual Hardware tab, expand the CPU section.
3. Check the box labeled "Expose hardware-assisted virtualization to guest OS."
4. Click OK.

Step 4: Verify nested virtualization is working inside the guest

1. Start the virtual machine and log in to the guest operating system.
2. Install a system information tool such as CPU-Z or Speccy, or use a command-line utility to check for virtualization extensions.
3. Confirm that the guest OS reports Intel VT-x or AMD-V as available. For example, in a Windows guest, open Task Manager > Performance > CPU and look for "Virtualization: Enabled."
4. Launch your intended nested hypervisor (e.g., WSL 2, Hyper-V Manager, or another VMware VM). The "VT-x/EPT not supported" error should no longer appear.

Troubleshooting common nested virtualization problems

Virtualization option missing in BIOS

If you cannot find the virtualization setting in BIOS/UEFI, first confirm that your CPU model supports Intel VT-x or AMD-V. If it does, update the motherboard firmware to the latest version. Some older firmware versions hide or omit the option.

Error persists after enabling

If the "VT-x/EPT not supported" error still appears after following all steps, re-check the conflicting Windows features on the host. Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform must all be off. Also verify that Virtualization-Based Security (VBS) and Memory Integrity are disabled. A host reboot is required after each change.

Slow VM performance

Nested virtualization adds overhead. Allocate sufficient CPU cores and memory to the guest VM, at least 2 CPU cores and 4 GB of RAM for a nested hypervisor. Avoid overcommitting resources on the host. For workloads like running WSL 2, consider assigning 4 or more cores and 8 GB of RAM to the outer VM. If you need to use a VHD in VMware Workstation, nested virtualization must be enabled first so that the guest OS can access the hardware virtualization extensions required by Hyper-V or other hypervisors that manage VHD files.