Instant Virtual Machine Related

• On vSphere 8.0, when Instant Virtual Machine creates the Guest OS information for the Windows 11 VMs, it appears as Windows 10.
• On vSphere 8.0, when Instant Virtual Machine creates the Guest OS information for the Rocky Linux and AlmaLinux VMs, it appears as Red Hat Enterprise Linux 8.
• Unable to run Linux instant VM job on the ESX server.

Symptom

When vCenter manages the ESX server, running Linux instant VM job on the ESX server and selecting a VDS network fails.

Solution

The Instant VM is unable to locate IP. As a workaround, specify instant VM job to vCenter and then select the ESX server.

• The IVM job cannot work for SLES 15 with XFS volume.

Symptom

The Linux Instant VM job fails when performing the IVM job for SLES 15 with XFS volume.

Solution

Perform a BMR job with Cent OS 7.5+ Live CD.

• The name and location of the Instant VM are not displayed as expected.
• Symptom
• When you use the ESX information to login and select a resource pool as the location of the Instant VM, the Instant VM is located under the ESX host, and not in the resource pool. If you delete the Instant VM from Console and recreate an Instant VM with the same name, a suffix (1) is added to the name of the Instant VM and not to the timestamp as expected.
• Solution
• The issue occurs due to vCenter managing the ESX Server. Instead, use the vCenter login information to create the Instant VM.

• If you add a node using the IP address, create a backup plan, and specify a shared folder as the backup destination. The Instant VM creation may fail from the node list view. However, you can create the Instant VM from the destination view. Alternatively, you can also update the node using the host name and try to create the Instant VM again.
• When you create an Instant Virtual Machine (Instant VM) using the recovery point that has mirrored system volume, you may get some error messages such as, a Black Screen of Death.
• In Hyper-V, the Instant VM fails to boot after restarting the recovery server.
• Symptom
• When you start the Instant VM and restart the Hyper-V recovery server, the Instant VM may fail to boot.
• Solution
• To resolve the boot failure, restart the Instant VM.

• In Windows Server 2012, creating NFS on a dynamic disk may fail. To resolve this issue, you can use a basic disk or apply a patch.
• For more information on the patch, see the KB article from Microsoft.
• Unable to verify the virtual machine heartbeat when the destination hypervisor is Windows 2016 Hyper-V.
• Symptom
• If you have not applied any update on the source machine related to Hyper-V heartbeat, then the heartbeat of virtual machine fails to detect on Windows 2016 Hyper-V and the following warning message is displayed in the activity log:
• Integration Service ISO file [C:\Windows\System32\vmguest.iso] does not exit.
• Solution
• As a workaround, update the integration services through Windows update. The vmguest.iso image file is no longer needed and is not included with Hyper-V on Windows Server 2016.
• To install the update manually, refer to the KB article.

• The Instant VM on VMware fails to boot up.

Symptom

• The Instant VM on VMware fails to boot up and enters into the EFI environment if the source node is a Windows 2008 Server and boots from the EFI system.
• Solution
• Add a Windows boot entry into the EFI environment manually.
• Follow these steps:
  1. After the VM boots into the EFI environment, enter details for one of the following options:
     • For ESXi 5.x: Boot Maintenance Manager
     • For ESXi 6.x: Enter Setup
  2. Enter Configure boot options.
  3. Select Add boot option.
  4. Select the file bootmgfw.efi that is available at the folder EFI\Microsoft\Boot\ on the EFI partition.
  5. Enter Windows Boot Manager and select Commit Changes and exit.
  6. Select Reset the system to reboot the virtual machine.

  Using the Windows Boot Manager option, Windows boots up successfully.

• The Instant VM creation fails when the Windows volume that is used as VMware NFS on the recovery server is formatted.
• Symptom
• If you have assigned Windows volume as an NFS shared folder and provided the shared volume path as Instant VM file path, the Instant VM creation fails when you format the Windows volume. The issue occurs because the ESXi host fails to add the NFS data store and VMware displays the following error message:

VMware create VM failed.

• The following error log is displayed in the vmkernal.log file:

No underlying device for major, minor

• Solution
• To resolve this issue, perform following steps on the recovery server:
1. Open Administrative Tools from Control Panel, System and Security, Administrative Tools.
2. Click Services.
3. From the Services dialog, right-click Server for NFS and then click Stop Service.
4. The Service stops.
4. Again right-click Server for NFS and then click Start Service.
5. The Service starts.
5. Use the volume to create an Instant VM again.
6. The Instant VM gets created.

• Instant VM fails to display the list of recovery points.

Symptom

• If you create an Agentless backup plan and specify a local path as the backup destination, then Instant VM fails to display the list of recovery points.
• Solution
• To resolve this issue, use shared folder as the backup destination.
• Instant Virtual Machine fails to boot up.

Symptom

Instant Virtual Machine fails to boot up and displays the following error message:

Failed to communicate with deduplication Data role on server xxxxx. Network error = [Connection timeout.].

Failed to process the virtual disk file [E:\test\UDPIVM_liuxi02-win16_{9B72149A-FB17-4736-9D98-0410C9462C3B}\InstantVM\disk2061091111.VHDX] with the disk GUID [{20461698-FF5E-46B0-8DB3-1571DE46E752}]. Error message: No waiter is present for the filter's reply to this message

Failed to process the virtual disk file [E:\test\UDPIVM_liuxi02-win16_{9B72149A-FB17-4736-9D98-0410C9462C3B}] with the disk GUID [{20461698-FF5E-46B0-8DB3-1571DE46E752}]. Error message: Failed to read disk data from the backup destination

This issue occurs when the following conditions are met:

• Create Instant VM to Hyper-V, and the target hypervisor is Windows Hyper-V 2012 R2.
• The backup destination is Recovery Point Server, the Recovery Point Server is installed inside a virtual machine, and the virtual machine is on the same Hyper-V server.
• The VM files folder that is set in creating InstantVM phase and the VHDX files of Recovery Point Server are on the same volume of that Hyper-V server.

Note: The issue does not occur on Windows Hyper-V 2016.

Solution

As a workaround, perform one of the following steps:

1. Set the VM files folder on a different volume when you create Instant VM from Console.
   
2. Use another Windows Hyper-V server as the destination.