Migration completed successfully but server is not pinging

Complete or stop the existing replication record, refresh VMware discovery, and prepare the source Linux initramfs with Hyper-V drivers before enabling replication again.

1. Remove the stale migration state

Deleting the Azure Local VM, disks, and network resources does not remove the protected item maintained by Azure Migrate. Because the replication artifacts—including the seed disks—were manually deleted, the existing replication cannot safely be reused; stop it and begin initial replication again. Microsoft specifically notes that deleting a seed disk can require stopping and re-enabling replication. ^1^

1. In the Azure portal, open the Azure Migrate project.
2. Go to Migration tools → Azure Local migration → Replications.
3. Find LPAL0199SECSZ02.
4. If the previous migration still shows as migrated, select Complete migration.
5. Otherwise, select Stop replication and wait for its removal from Replications.
6. Use Forcefully complete migration or Forcefully stop replication only if the normal operation fails. Forceful removal can leave artifacts behind and should be a last resort. ^1^

Do not delete any further seed disks or replication resources manually.

2. Refresh the source VMware inventory

The powered-off value is discovery inventory, not a live indication that the guest is currently unreachable.

1. Confirm the source VM remains powered on in vCenter and has VMware Tools installed; both are required during Azure Local discovery and migration. ^2^
2. Open the source Azure Migrate appliance Configuration Manager.
3. Confirm that its vCenter discovery source and credentials remain valid.
4. Select Start Discovery and wait for the green completion checkmark.
5. In the Azure portal, open Azure Migrate → Servers, databases and web apps and select Refresh to expedite synchronization. ^3^
6. Verify that the VM now appears as powered on and is selectable under Migration and modernization → Replicate.

If discovery does not update, verify the VMware discovery service on the source appliance:

Get-Service -Name amvmwdiscoverysvc,asrgwy,asrmgmtsvc

# Start only services that are stopped:
Start-Service -Name amvmwdiscoverysvc
Start-Service -Name asrgwy
Start-Service -Name asrmgmtsvc

These services must be healthy on the source appliance. ^3^

3. Prepare the Linux VM before replicating again

The dracut-initqueue timeout and unavailable root logical volume are consistent with the documented Azure Local issue in which the Linux initramfs lacks the Hyper-V storage and bus drivers needed after migration. Apply the fix to the working VMware source VM before retrying. ^4^

Run as root:

uname -r
lsinitrd | grep -Ei 'hv_(vmbus|netvsc|storvsc|utils)'

cp -a /boot/initramfs-$(uname -r).img \
      /boot/initramfs-$(uname -r).img.pre-azure-local

printf '\nadd_drivers+=" hv_vmbus hv_netvsc hv_storvsc hv_utils "\n' \
  >> /etc/dracut.conf
dracut -f -v
lsinitrd | grep -Ei 'hv_(vmbus|netvsc|storvsc|utils)'

Also update /etc/fstab to reference persistent volume identifiers rather than transient device names before migration. ^3^

Then reboot the VMware source once and confirm it still starts normally.

4. Replicate and validate again

1. Select Migration and modernization → Replicate.
2. Choose Azure Local, VMware vSphere, the applicable source appliance, and LPAL0199SECSZ02.
3. Allow initial replication to complete until Migration status becomes Ready to migrate. ^2^
4. Perform a test migration or controlled migration and verify console boot, LVM volumes, networking, and the Zeek services.
5. Only after validation, select Complete migration instead of manually deleting replication artifacts. ^5^

If the VM remains unavailable after discovery completes, collect the source-appliance logs from C:\ProgramData\MicrosoftAzure\Logs\HyperV\Discovery, plus the replication Job ID, and open a Microsoft support case. ^3^

References

1. FAQ - Migration of Hyper-V and VMware VMs to Azure Local using Azure Migrate
2. Discover and replicate VMware VMs for migration to Azure Local using Azure Migrate
3. Troubleshoot issues migrating VMs to Azure Local via Azure Migrate
4. Known issues in Azure Migrate for Azure Local
5. Migrate VMware VMs to Azure Local using Azure Migrate