Troubleshoot a Broken Azure VM using Nested Virtualization in Azure (RDFE)


Please note that 3rd party virtualization software(s) for Windows 2016 Nested Virtualization feature is not supported. Only Hyper-V is currently supported.

Also note that as of right now, Nested Virtualization is only available in the following geographic locations:

US
-West 2
-East

Europe
-West

Asia Pacific
-Southeast

Reference Links:
Nested Virtualization in Azure
New DV3 and EV3 Series Virtual Machines

  1. Create a new Recovery VM
    1. OS: Windows Server 2016 Datacenter
    2. Size: Any V3 series with at least 2 cores
    3. Same Location, Storage Account and Resource Group as the Broken VM
    4. Select the same storage type as the broken VM (Standard or Premium)
  2. Delete the Broken VM. Ensure to KEEP all attached disks
  3. Once the Broken VM is deleted navigate to the Recovery VM
  4. Select Disks
  5. Select Attach Existing
  6. Browse to the location of the Broken VMs VHD
  7. Select the Broken VMs VHD and click OK
  8. Once the disk has successfully attached RDP to the Recovery VM
  9. In Server Manger select Manage -> Add Roles and Features
  10. For Installation Type select Role-based or feature-based installation
  11. Ensure the Recovery VM is selected
  12. Select the Hyper-V role

  13. Select Next on the Features Screen.
    1. If a Virtual Switch is available, select it and continue. Otherwise select Next and continue without a switch
  14. On the Migration Page select Next
  15. On the Default Stores Page select Next
  16. Check the box to restart the server automatically if required
  17. Select Install
  18. Allow the Server to install the Hyper-V role. This will take a few mins and the server will reboot automatically. You can monitor the reboot cycle using the Boot Diagnostics Tab in the Azure Portal
  19. Once the VM starts back up RDP back into it
  20. Open Disk Management and ensure the VHD of the Broken VM is set to Offline
  21. In Server Manger select the Hyper-V role
  22. Right click on the server and select the Hyper-V Manger
  23. In the Hyper-V manager right click on the Recovery VM and select New -> Virtual Machine
  24. Select Next
  25. Name the Virtual Machine and select Next
  26. Select Generation 1
  27. Leave the startup memory at 1024MB unless your VM requires more.
  28. If applicable select the Hyper-V Network Switch that was created. Else just move on to the next page
  29. Chose the option to Attach a Virtual Hard Disk Later
  30. Select Finish and the VM will be created
  31. Right click on the VM we just created and select Settings
  32. Select IDE Controller 0
  33. Select Hard Drive and click Add
  34. Under Physical Hard Disk select the VHD of the broken VM we attached to the Recovery VM
    1. If you do not see any disks listed it is because the VHD attached to the Recovery VM is set to Online. Refer back to step 22
  35. Select Apply and OK
  36. Double Click on the VM and Start it
  37. Depending on your scenario, apply any troubleshooting/ mitigations steps now that you have console access
  38. Once you get the VM back online shutdown the VM in the Hyper-V manager
  39. Go back to the Azure Portal
  40. Select the Recovery VM
  41. Select Disks
  42. Detach the now fixed VHD  from the Recovery VM
  43. Proceed to rebuild the now fixed VM. Refer to How to Rebuild an Azure VM from an Existing Disk OS disk

Comments (0)

Skip to main content