How to Enable Nested Virtualization in Hyper-V Using PowerShell

Nested virtualization is a powerful feature that allows you to run a virtual machine (VM) inside another VM. This capability is particularly useful for developers and IT professionals who want to test software or configurations in a contained environment without affecting their main system. In this article, we will walk you through the process of enabling nested virtualization in Hyper-V using PowerShell, specifically for a VM named “Windows 11 dev environment.” Whether you are setting up a complex test environment or just exploring the capabilities of virtualization, this guide will help you get started.

Prerequisites

Before you begin, there are a few requirements that need to be met:

1. Hyper-V Enabled: Ensure that Hyper-V is installed and enabled on your host machine. This feature is available on Windows 10 Pro, Enterprise, and Education editions, as well as on Windows Server 2016 and later.
2. Hardware Support: Your CPU must support Intel VT-x or AMD-V for hardware-assisted virtualization. Additionally, it should support Second Level Address Translation (SLAT).
3. Windows 11 VM: The virtual machine on which you are enabling nested virtualization should be running Windows 11. Ensure it is set up and correctly configured in Hyper-V. For this example we will be using a VM named Windows 11 dev enviroment. If needed, here you can learn How to Enable and Create a Hyper-V VM in Windows 11 for Development.
4. PowerShell: Familiarity with PowerShell is helpful as the commands for enabling or disabling nested virtualization will be executed through this interface.

Step 1: Launch PowerShell as Administrator

To modify the settings of a VM in Hyper-V, you need administrative privileges. Right-click on the Start button and select “Windows PowerShell (Admin)” from the context menu. Confirm any prompts to allow PowerShell to run with elevated privileges.

Step 2: Verify Your VM

Before proceeding with enabling nested virtualization, it’s essential to ensure that your target VM, “Windows 11 dev environment”, is correctly recognized by Hyper-V. Execute the following command to list all virtual machines:

Get-VM

Locate “Windows 11 dev environment” in the output list to confirm that it is ready for configuration.

Step 3: Enable Nested Virtualization

With your VM verified, you can now enable nested virtualization. Run the following command in PowerShell:

Set-VMProcessor -VMName 'Windows 11 dev environment' -ExposeVirtualizationExtensions $true

This command sets the processor of the VM named “Windows 11 dev environment” to expose its virtualization extensions, thus allowing the VM to host other virtual machines.

Step 4: Start Your VM

After enabling nested virtualization, start your VM to apply the changes. Use the following PowerShell command:

Start-VM -Name 'Windows 11 dev environment'

Once the VM is running, you can proceed to install and configure the inner VM as needed.

Step 5: Verifying Nested Virtualization

To verify that nested virtualization is working inside your VM, you can check the presence of the Hyper-V feature within the VM itself or attempt to create another VM inside the “Windows 11 dev environment.” If the setup is successful, you will be able to run a nested VM without any issues.

Step 6: Disabling Nested Virtualization

If you need to disable nested virtualization for any reason, such as improving the performance of the host VM or troubleshooting, you can execute the following command:

Set-VMProcessor -VMName 'Windows 11 dev environment' -ExposeVirtualizationExtensions $false

This will reverse the earlier action and prevent the VM from being able to host other VMs.

Final Thoughts

Nested virtualization is an invaluable tool for testing and development, providing a flexible and isolated environment. By following the steps outlined above, you can enable and manage nested virtualization in your “Windows 11 dev environment” using PowerShell. Remember to operate within the limits of your hardware and ensure that all system requirements are met to maintain a stable and efficient virtualization setup.

Happy virtualizing!