RecoverPoint for Virtual Machine: EFI boot causes the shadow VM to go into a reboot cycle if network boot is enabled causing DRU

요약: EFI boot causes the shadow VM to go into reboot cycle if network boot is enabled causing DRU.

이 문서는 다음에 적용됩니다. 이 문서는 다음에 적용되지 않습니다. 이 문서는 특정 제품과 관련이 없습니다. 모든 제품 버전이 이 문서에 나와 있는 것은 아닙니다.

증상

Copy VM in reboot cycle

RecoverPoint for Virtual Machines Consistency Group (CG) containing the rebooting VM regulated.

EFI BIOS with PXE boot enabled on production VM

Copy VM fails to boot with error:

 Info: There isn't enough memory available to create a ramdisk device.

Figure 1: VM Boot Error

원인

The ResourcePak SMURF Boot device (Floppy Drive) does not support EFI boot. This means when the production VM is configured with EFI instead of BIOS, and Network Boot is enabled, ResourcePak SMURF VM slips down the boot order. At PXE boot, if a PXE server is found on the network it goes for Cyclic Reboot, which causes DRU.

해결

Workaround:
There are three possible workarounds available:

Use BIOS firmware instead of EFI for Production VMs.
Boot the DR VM in a Network where the PXE boot server is not reachable (The PXE Boot server IP can be found in the error message.

Windows Boot Manager (Server IP: xxx.yyy.zzz.jjj)

Disable PXE Boot from boot manager of copy VM.

NOTE: For the third workaround, if Image Access is enabled, the PXE boot is enabled again on the copy VM by default. Hence, after each Image Access, PXE Boot must be disabled in BIOS.

Resolution:
Dell engineering is investigating this issue. A permanent fix is in progress and this article will be updated when more information becomes available. Contact the Dell Customer Support Center or your service representative for assistance and reference this solution ID.