It happened: in build 10565 Windows Insider Preview rolled out the first preview guest virtualization in Hyper-V. The news is interesting, but it didn’t seem to be there, which is rather strange.

Since this is the first swallow there are a number of limitations:
1. Both hypervisors should be on the preview version 10565, otherwise “it will not take off”.
2. When running guest virtualization, the following functions will not be available for the virtual machine: dynamic memory, memory change “on the fly” (new function in Win10), save \ restore, live migration.
3. When you enable guest virtualization, you must enable MAC Spoofing, otherwise the network in the guest guest will not work.
4. Virtualization Based Security must be disabled before enabling the ability to use guest virtualization.
5. Intel processors only (need Intel-VT).
6. They say that you need a lot (!) Of RAM, but later in the post they write that 4 GB on a laptop is enough;)
')
How to turn on:
1. Create a virtual machine, install Windows, turn off.
2. Run the
script . The script itself will make all the settings (and correct the limitations described above, asking for your consent).
3. Turn on the virtual machine, install Hyper-V using powershell Direct from the host:
Invoke-Command -VMName "" -ScriptBlock { Enable-WindowsOptionalFeature -FeatureName Microsoft-Hyper-V -Online; Restart-Computer }
4. Turn on MAC Spoofing:
Set-VMNetworkAdapter -VMName -MacAddressSpoofing on
5. - .
6. ???
7. .
" ":
1. .
Invoke-WebRequest raw.githubusercontent.com/Microsoft/Virtualization-Documentation/master/hyperv-tools/Nested/Get-NestedVirtStatus.ps1 -OutFile ~/Get-NestedVirtStatus.ps1
~/Get-NestedVirtStatus.ps1
2. "Virtual Machine Connection", .
.