Win10 10565 How to run virtual machine

in virtual machine Earlier this year, Microsoft announced that it will develop a new technology called nested virtualization technology, so users can run Hyper-V in Hyper-V virtual machine. Container, that is, running the Hyper-V virtual machine in the Hyper-V virtual 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 winding, Hyper-V virtual machine running depends on hardware virtualization technology support, 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 exposes virtualization extensions to clients, so clients can have their own virtual machines.

As shown in the figure below, 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 should be noted that this feature is still in the preview stage, so there will inevitably be some problems, not for production environments. The following are known issues:
The nested versions must be the latest version, and Windows Server 2012 R 2 and Windows 10 Preview versions prior to 10565 are not available.
Once the virtualization nesting technology is enabled, the following features will not be compatible. Using these features will cause the virtual machine to stop working or the function will not work:
-dynamic memory;
-Runtime memory adjustment;
-When applying checkpoints in a virtual machine, it will not work;
-Dynamic migration function;
MAC spoofing technology must be enabled to ensure normal network connection for clients;
Currently only supports Intel VT-x virtualization Technology;
The computer needs to have enough memory!
Enable the virtualization technology nesting method:
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
Enable Hyper-V functionality in the client;
Enable client network support:
Run the following Powershell command on the host machine:< Br>Set-VMNetworkAdapter -VMName -MacAddressSpoofing on
At this point you can be at the client Continue to install the nested client.