You need to ensure that containers that run on VM1 can …

Did anybody read the book 70-740???

Before you install Hyper-V on the virtual machine, you must provide its virtual
processor with access to the virtualization technology on the physical computer. To do this,
you must shut down the virtual machine and run a command like the following on the
physical host, in an elevated PowerShell session:
Click here to view code image
set-vmprocessor -vmname server1 -exposevirtualizationextensions
$true
In addition, you must make the following configuration changes on the VM that function
as a Hyper-V host. Each is given first as the location in the VM Settings dialog box in
Hyper-V Manager, and then as a PowerShell command:
On the Memory page, disable Dynamic Memory.
Click here to view code image
set-vmmemory -vmname server1 -dynamicmemoryenabled $false
On the Processor page, set Number Of Virtual Processors to 2.
Click here to view code image
set-vmprocessor -vmname server1 -count 2
On the Network Adapter/Advanced Features page, turn on MAC Address Spoofing.
252
Click here to view code image
set-vmnetworkadapter -vmname server1 -name “network adapter”
-macaddressspoofing
on
Once you have made these changes, you can start the VM, install the Hyper-V role, and
create nested virtual machines. While the VMs run on the nested host, there are some
Hyper-V features that do not work, such as live memory resizing, checkpoints, Live
Migration, and Save/Restore.