Solved: Unable to Access the VM After Replication Using Do... - Page 2

ejcs001 · 06-28-2021 06:59 AM

I am getting the prompt above in the serial console connection to a GCP VM after using Double Take replication software from on-premise to GCP. Any idea what happened?

BdsDxe: loading Boot0005 "Windows Boot Manager" from HD(2,GPT,70B9298F-6A7E-40B4
-993C-881879AC1F4C,0x8000,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0005 "Windows Boot Manager" from HD(2,GPT,70B9298F-6A7E-40B
4-993C-881879AC1F4C,0x8000,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi

UEFI: Attempting to start image.
Description: Windows Boot Manager
FilePath: HD(2,GPT,70B9298F-6A7E-40B4-993C-881879AC1F4C,0x8000,0x32000)/\EFI\Mic
rosoft\Boot\bootmgfw.efi
OptionNumber: 5.

fadya

The message indicates that UEFI detected Windows Boot Manager. The message is not necessarily an error. What you care about is the messages after especially from serial port2. You can verify this output as an example.

As for migration from on-prem it might be better to use the Compute Engine migration tool as you may have issues with licenses (current approach). Generally you can not bring your own license (the Operating system physical core license) unless if you are using sole-tenant nodes and that might not fit your needs in terms of costs as you are reserving the physical machine as a whole.

View solution in original post

Unable to Access the VM After Replication Using Double Take