Win10 10565 Preview New Features Running Virtual Machines in Virtual Machines

Before this year, Microsoft announced that it will develop a new technology called nested virtualization technology so that users can run Hyper-V containers in Hyper-V virtual machines, ie in Hyper-V virtual Run the Hyper-V virtual machine in the machine. Earlier versions of this feature have now been released in Microsoft's Win10 Preview 10565. It should be noted that this function is for the system to bring the Hyper-V virtual machine.

This feature essentially virtualizes some of the hardware features required to run a hypervisor in a virtual machine. It sounds a bit sloppy, and Hyper-V virtual machines run on hardware virtualization technologies such as Intel VT-x and AMD-V. Typically, once Hyper-V is installed on the host, the hypervisor hides the technology from the client and prevents the guest virtual machine from installing Hyper-V. As shown in the following figure, in the previous version, the host's Hyper-V hypervisor has full control of the virtualization extension, and the function is not open to the client.

In the latest version, the host's Hyper-V hypervisor opens the virtualization extension to the client, so the client can have its own virtual machine.

As shown in the following figure, you can see that a Hyper-V virtual machine is running on a computer, and a virtual machine is running inside the Hyper-V virtual machine.

It is important to note that this feature is currently in the preview phase, so there are inevitable problems that may not be used in a production environment.

The following are known issues:

• Nested versions must be the latest version, Windows Server 2012 R 2 and Windows 10 Preview versions prior to 10565 are not available.

• Once the virtualization nesting technology is turned on, the following features will not be compatible, and using these features will cause the virtual machine to stop working or the function will not work:

-dynamic memory;

-Runtime memory adjustment;

-will not work when applying checkpoints in a virtual machine;

-dynamic migration function;

• MAC must be enabled Deception technology can guarantee the client's normal network connection;

• Currently only supports Intel VT-x virtualization technology;

• The computer needs to have enough memory!

Enable the nesting method of virtualization technology:

• Create a Hyper-V virtual machine, then close it;

• Run the virtualization nesting technology to open the script (Click here to download):

Invoke-WebRequest https://raw.githubusercontent.com/Microsoft/Virtualization-Documentation/master/hyperv-tools/Nested/Enable-NestedVm.ps1 -OutFile ~/Enable- NestedVm.ps1

~/Enable-NestedVm.ps1 -VmName <VmName>

• Enable Hyper-V in the client;

• Machine Network Support:

Run the following Powershell command on the host machine:

Set-VMNetworkAdapter -VMName <VMName> -MacAddressSpoofing on

• It is now possible to continue installing nested clients in the client.

Related recommendation:

[Download]Win10 Build 10565 64-bit ISO image download (non-Microsoft official)!

Win10 build 10565 preview activation can use Win7/Win8.1 key