Fix a faulty Virtual Machine Using Nested Virtualization in Azure

Introduction

Azure is a platform for open-source cloud computing. It offers numerous cloud services, such as computation, analytics, storage, and networking. These services are available for users to choose from while creating and scaling new apps or using the public cloud to operate existing applications.

You can design your virtualization environments using nested virtualization, which permits you to run virtual machine (VM) instances inside other VMs.

If you have virtual machines (VMs) that cannot be run on Compute Engine, such as a disaster recovery system for an on-premises application that utilizes VMs to fail over to Compute Engine VMs. You could save time by using nested virtualization instead of porting your VMs to Compute Engine.

Step-by-Step Guide for troubleshooting faulty Virtual Machines and the Creation of Rescue Virtual Machines

Step 1: Sign into the Azure portal, In the VM Blade Copy the Public IP and RDP to the VM. If you will find a similar error as shown in the below Image, then follow step 2.

Step 2: Creation of the snapshot using the OS Disk and the snapshot to create the new OS disk.

1. In faulty VM and on the left side of VM Blade find Disks.
2. In Disks click on the description below the Disk name.
3. After clicking on the OS disk, Create a snapshot.

4. After creating the snapshot in the snapshot directory, Create a new disk with the same configuration.

Step 3: Creation of the Rescue VM and attach the disk created.

1. Create a rescue VM with no redundancy required in the availability zone.
2. Choose a windows server data center, with a min of Dv3 or Dv4 core processor.
3. Rescue VM should be in the same location as the Storage account of the faulty VM resides.
4. Select the RDP port and all the licenses required.
5. Attach the data disk created using a snapshot to the VM.
6. Keep all the settings to default.
7. Review and create the VM after validation is successful.

Step 4: Install Hyper-V in the rescue VM.

1. RDP to the Rescue VM.

2. Inside VM, search for disk Management.

3. In disk management, right-click on Disk 2 and make it offline.

4. In server Manager, Select Manage -> Add Roles and Features.

5. In the installation type select Role-based or feature-based installation.

6. In server roles, select Hyper-V, click install, and keep others to default. Proceed with next.

7. On the confirmation page, confirm the Check box to restart the server automatically and install.

8. It will take a few minutes to restart, there will be a connection lost to the VM, so you need to RDP again to the server.

Step 5: Create a new VM in the Hyper-V manager and attach the faulty disk.

1. Open Hyper-V manager and create a New VM.
2. Type the name of the VM and select next.
3. Select the Generation based on the faulty VM.
4. Keep all the settings to default and select virtual Hard disk to attach later.

5. Right-click on the VM we created and select the setting.

6. For Gen 1 select IDE Controller 0 and SCSI Controller for Gen 2.

7. Double-click on the VM and start IT, this will take some time.

8. Use the credential of the faulty VM to login.

9. In the VM run the command Regedit.

10. In Regedit, Navigate to HKEY_LOACL-MACHINE -> SYSTEM -> CurrentControlSet -> Control -> Terminal Server -> Winstation -> RDP -> In RDP change port number to 3389.

Step 6: Swap the OS disk of the faulty VM with the newly created OS disk.

1. Shut down the VM in the Hyper-V manager.
2. remove the repaired OS disk.
3. Replace the OS disk used by the VM with the repaired OS disk.
4. RDP to the faulty VM.

Conclusion

Nested Virtualization allows you to run Virtualization on a Virtual Machine. With the release of Windows Server 2016, features were added to Azure and Hyper-V virtual machines that can aid in problem-solving. Here when a client or customer working remotely faces RDP issues it will be difficult to resolve but with the help of Nested vitalization, we can repair a faulty Virtual machine easily.

About CloudThat