Editar

Compartilhar via

Nested virtualization in Azure Stack HCI

  • Artigo

Applies to: Azure Local, version 22H2

Important

Azure Stack HCI is now part of Azure Local. Product documentation renaming is in progress. However, older versions of Azure Stack HCI, for example 22H2 will continue to reference Azure Stack HCI and won't reflect the name change. Learn more.

Nested virtualization is a feature that lets you run Hyper-V inside a Hyper-V virtual machine (VM). This allows you to maximize your hardware investments and gain flexibility in evaluation and testing scenarios.

Important

Because Azure Stack HCI is intended as a virtualization host where you run all of your workloads in VMs, nested virtualization is not supported in production environments. For production use, Azure Stack HCI should be deployed on validated physical hardware.

Some scenarios in which nested virtualization can be useful are:

  • Running applications or emulators in a nested VM
  • Testing software releases on VMs
  • Reducing deployment times for training environments

Enable nested virtualization on a VM

To enable nested virtualization on a VM using Windows Admin Center:

  1. Connect to your cluster, and then in the Tools pane, select Virtual machines.

  2. Under Inventory, select the VM on which you want to enable nested virtualization.

  3. Select Settings, then Processors, and check the box for Enable nested virtualization.

    Check the box to enable nested virtualization on a VM

  4. Select Save processor settings.

To configure nested virtualization on a VM using PowerShell, see Run Hyper-V in a Virtual Machine with Nested Virtualization.

Nested virtualization processor support

Azure Stack HCI, version 21H2 adds support for nested virtualization on AMD processors. Now you can run nested virtualization on first generation EPYC processors or newer generations (Naples, Rome, Milan).

Prerequisites:

  • Azure Stack HCI, version 21H2
  • VM configuration version 10.0 or greater
  • An AMD EPYC processor with SVM enabled

Next steps

For more information, see also: