We have already mentioned new Azure VM series Dv3 and Ev3 which enable running VMs inside Azure VMs or just nested virtualization. Today we are going to get it configured and to run our first nested VM in Azure.
But before we start, let’s review some Dv3 and Ev3 facts:
they introduce Hyper-Threading Technology running on the Intel® Broadwell E5-2673 v4 2.3GHz processor and Intel® Haswell 2.4 GHz E5-2673 v3
they made shift from physical core to virtual CPUs (thanks to HT technology) to support larger VM sizes
they are the first Azure VMs running on Windows Server 2016 hosts
Dv3 VMs are up to 64 vCPUs and 256 GB RAM
Ev3 VMs are up to 64 vCPUs and 432 Gb RAM
they are currently available only for certain regions (West Europe, US East, US West 2, Asia Pacific Southeast)
they already come with ExposeVirtualizationExtensions enabled. we don’t need to enable CPU extensions as we have to do for on-premises WS2016 hosts
To get started with “nesting” you need to create one or more Dv3/Ev3 VMs in Azure within compatible region. For quick demo purposes, I created D2S_V3 VM with Windows Server 2016 DC , standard managed disk with no data disks attached.
TIP: actually you can , for instance, create 2 or more VMs , add data disks and configure storage spaces between them to achieve higher IO performance.
Then you need to install Hyper-V role and restart VM to apply changes
Install-WindowsFeature Hyper-V -IncludeManagementTools -Restart
Verify that Hyper-V role is installed and add internal switch. New adapter “vEthernet (switchname)” will be created under network connections list (ncpa.cpl)
Define a new IP address for this adapter (I’m using 192.168.0.0/24 subnet). This network will be used as a NAT gateway for new VMs in order to allow internet access from nested VMs.
#Check Hyper-V role state Get-WindowsFeature Hyper-V|ft InstallState, PostConfigurationNeeded #Add new internal switch New-VMSwitch -SwitchName "NSW01" -SwitchType Internal # IP Configuration for vNIC New-NetIPAddress -InterfaceAlias "vEthernet (NSW01)" -IPAddress 192.168.0.23 -PrefixLength 24
Configure NAT rule to provide “access” to our nested VMs
New-NetNat -Name Nat_VM -InternalIPInterfaceAddressPrefix 192.168.0.0/24
Now our nested VMs can assign IP addresses from 192.168.0.0/24 subnet (manual assignment). If you want to have dynamic IP assignment – create add. VM and configure DHCP.
When network configuration is done, add you first nested VM, run and check it’s status:
New-VM -Name Nested01 -MemoryStartupBytes 2GB -SwitchName NSW01 -Generation 2 -NewVHDSizeBytes 70GB -NewVHDPath C:\VMs\Nested01\OS.VHDX
Using my Azure File share I installed WS2016 Essentials inside of Nested01 VM and configured IP address from subnet above. As you can see, after IP configuration my nested VM can access Internet via created NAT gateway previously (see ping output).
New-NetIPAddress -InterfaceAlias “Ethernet” -IPAddress 192.168.0.20 -DefaultGateway 192.168.0.23 -PrefixLength 24 Set-DnsClientServerAddress -InterfaceAlias Ethernet -ServerAddresses 22.214.171.124
Final result (yeap, Simpsons again and again)
Homer – my Hyper-V host (Azure Dv3 VM)
Bart – nested VM (WS2016 Essentials)
Cool? Go ahead and test Azure Stack using it’s deployment kit . I’ll cover it in my next posts. Keep in touch and happy Azure VMs nesting!
4 thoughts on “How to enable nested virtualization in Azure”
What if my environment is in Cluster. I would have different Gateways. Two nodes two Gateways
When moving a VM I will have to change the gateway.
Is there any solution in this case?
I don’t think that is a good idea to use nested in such configuration. What’s purpose? Any details?
I gave up, it was a lab I was trying to prepare. thanks