Nested virtualization means that you can run Hyper-V inside a VM, opening up unimaginable flexibility for testing advanced infrastructure setups, demos, or studying environments, all with out further {hardware}.
First, make sure you’re operating a Hyper-V host able to nested virtualization and have the Home windows Server 2025 VM on which you wish to allow as a Hyper-V host prepared.
To get began, open a PowerShell window in your Hyper-V host and execute:
Set-VMProcessor -VMName "" -ExposeVirtualizationExtensions $true
Exchange
This command configures Hyper-V to permit nested virtualization on the goal VM.
Boot up the Home windows Server 2025 VM that you just wish to configure as a Hyper-V host. Within the VM, open Server Supervisor and try to put in the Hyper-V position by way of Add Roles and Options. More often than not, this could work straight away. Nonetheless in some circumstances you may hit an error stating:
“Hyper-V can’t be put in as a result of virtualization help isn’t enabled within the BIOS.”
To resolve this error run an elevated PowerShell session contained in the VM on which you wish to allow Hyper-V and run the command:
bcdedit /set hypervisorlaunchtype auto
This command ensures the Hyper-V hypervisor begins up appropriately the following time you boot.
Restart your VM to use the change. After the reboot, head again to Add Roles and Options and check out putting in Hyper-V once more. This time, it ought to proceed easily with out the BIOS virtualization error.
As soon as Hyper-V is put in, carry out a last reboot if prompted. Open Hyper-V Supervisor inside your VM and also you’re now able to run check VMs in your nested setting!
