The following issues have been observed for the migration of a Windows Server Failover Cluster to VMs on different hosts in a VMware cluster.
Issue: When the workload reaches the Configuring NICs step, the migration stalls. The VM does not appear to have a network connection. This problem occurs if the NIC order has changed and the NICs are improperly assigned to the opposite network (NIC1 on heartbeat and NIC2 on data network).
Workaround: In the vSphere Web Client, reconfigure the networks assigned to the NICs. Assign NIC1 to the data network. Assign NIC2 to the heartbeat network. See Section C.3.5, Configure VM NICs for the Heartbeat and Data Networks.
Issue: When the job reaches the Configure Target Machine step, the virtual machine’s console returns to the boot prompt of the PlateSpin ISO image. For workloads with UEFI firmware, it might boot to a screen with no menus.
Workaround: If the workload has BIOS firmware, the boot prompt eventually times out and proceeds to boot with the next disk, which is the Windows system disk. Wait for a few minutes until it proceeds on its own.
If the workload has UEFI firmware, the boot prompt or menu will not time out.
Monitor the migration job in Jobs view of PlateSpin Migrate Client.
When the job reaches the Configure Target Machine step, the virtual machine’s console returns to the boot prompt of the PlateSpin ISO image.
Shut down the virtual machine and reconfigure it to boot from disk rather than from the boot image.
Power on the virtual machine.
The migration job resumes, reboots the target, and completes the workload configuration.