Common Issues and Solutions for VMware Converter P2V Migration

During P2V (Physical-to-Virtual) migration, failures can occur despite careful preparation. Below are common issues and their solutions.

Key Stages in the Migration Process

1. 0%-5%: Creating the target virtual machine
2. 5%-6%: Preparing disk cloning
3. 6%-95%: Cloning data
4. 95%-97%: Finalizing cloning
5. 97%-99%: Customization and reconfiguration
6. 99%-100%: Installing VMware Tools or booting the VM

🔹 Note: The most common failure point is 97%, often due to network issues, DNS resolution errors, or missing Windows services.

---

Common Issues and Fixes

1. Migration fails quickly at 97%

✅ Solution:

• Ensure the source server can resolve the target server’s hostname (check DNS settings).
• Verify that the following services are running:

Workstation, Server, TCP/IP NetBIOS Helper, VMware Converter services

For Windows XP/2003, ensure Volume Shadow Copy service is set to “Manual”

• Test the required ports using:

telnet <VC/ESX_IP> 902 
telnet <VC/ESX_IP> 443

Ensure the source machine can reach the VMware server on port 902/443.

• Restart the source machine, especially if it is running Windows NT/2000.

2. Migration is slow and fails at 97%

✅ Solution:

• Check network speed and ensure duplex mode is correctly set.
• Remove any OS installation images attached to the VM.
• Run chkdsk to check for disk errors:

chkdsk /f /r

• Ensure at least 200MB of free space on the system partition.
• Verify registry settings:

Navigate to HKLM\HARDWARE\DEVICEMAP\SERIALCOM

If there are more than two COM ports, delete the extra ones (backup first).

3. Migration completes, but the VM fails to boot (BSOD)

✅ Solution:

• Check Boot.ini:

Attach the disk to another VM and verify the disk order in Boot.ini is correct.

• Verify SCSI Controller:

Ensure the correct SCSI type is selected (BusLogic or LSI Logic).

• Try Safe Mode:

If the VM boots into Safe Mode, check for hardware or driver conflicts.

---

Optimizing Performance for the New Virtual Machine

1. Remove unnecessary hardware (floppy drives, serial/parallel ports, USB controllers).
2. Adjust vCPU count (1 vCPU is usually sufficient).
3. Update HAL (Hardware Abstraction Layer):

Go to Device Manager → Computer → Update Driver → Select ACPI Uniprocessor (for single CPU).

4. Remove old ghost devices to avoid IP conflicts:

SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc

Open Device Manager → Show hidden devices → Uninstall grayed-out devices → Reboot.

---

Conclusion

vCenter Converter P2V migration failures often occur at 97%, primarily due to network issues, disk errors, or driver conflicts. By checking logs, optimizing network settings, and cleaning up the system, you can increase the success rate and ensure VM stability.😊😊