As demand increased, i would like to make a quick tutorial on what to look when you want to setup Azure Stack Development Kit (ASDK) on a nested virtualization environment, for purpose such as home lab or evaluation purposes.
Being on Nested Virtualization, gives you the flexibility on meeting the ASDK hardware requirement.
My physical server specification as below:
Dell EMC R630
1 x Intel Xeon E5-2630 v4 (10 cores)
2 x 400GB SSD (RAID 0)
1 x 1.2TB SSD
As you can see, i do not satisfy the needs for data disks from official document, yet with VM, i can present as many disks as i need.
I will be using Windows Server 2016 Datacenter as my OS, installed on OS disks.
Let’s jump right in where you should looks out and configure to get this working:
- Deploy a new VM. 12 vCPU, 64GB RAM, mount the CloudBuilder.vhdx, and 3 data disks of >150GB.
- Extend CloudBuilder.vhdx to at least 181GB
- Enable MAC Address Spoofing, make sure internet connectivity is available for VM
- Disable Time Synchronization
- Start the VM. Edit host name if you need to, double check network connectivity with Internet
- I prefer to use script options to deploy my ASDK
- Download the GUI and run through it. At the last step, copy the command line for deployment to run it in ISE
- As soon as the deployment starts, you’ll need to use ISE to edit physicalserver test. Use ISE to edit this C:\CloudDeployment\Roles\PhysicalMachines\Tests\BareMetal.Tests.ps1
- Line: 262-263 “!Microsoft**” “!Vmware**”
- Line: 598 & 610 delete ‘not’
- That’s all! Grab a coffee and wait for 4 hours!
Once it is deployed, continue to follow official guide to Register Azure Stack with Azure, create offers and subscriptions, and login as Tenant!
Next blog shall talk about how to stop-azurestack to prepare for reboot or shutdown sequence.