How to use VMware vCenter Converter for P2V migration

Prerequisites to perform P2V & V2V of Powered on Machine

  • Ensure that the Converter Standalone server machine able to access to the Windows source machine via network.
  • Stop or disable anti-virus software running on the source machine
  • Prepare local Administrator account on source machine
  • Allow following TCP and UDP ports in Firewall:
PortProtocolSourceDestinationPurpose
22TCPConverter Standalone serverpowered-on source machineUsed to establish an SSH connection between the Converter Standalone server and the source Linux machine
137UDPConverter Standalone serverpowered-on source machineFor hot migration. Not required if the source computer does not use NetBIOS
138UDPConverter Standalone serverpowered-on source machineFor hot migration. Not required if the source computer does not use NetBIOS
139TCPConverter Standalone serverpowered-on source machineFor hot migration. Not required if the source computer does not use NetBIOS
443TCPConverter Standalone servervCenter ServerRequired only if the conversion destination is a vCenter Server
443TCPConverter Standalone clientConverter Standalone serverRequired only if the Converter Standalone server and Linux client components are on different machines
443TCPConverter Standalone clientvCenter serverRequired only if the Converter Standalone server and client components are on different machines
22TCPPowered-on Source Linux machineESX/ESXi HostUses secure connection port 22 to Host
443,902TCPPowered-on Source Windows machineESX/ESXi HostRequired for data transfer to destination ESX/ESXi host Note: – Port 902 is required if destination is vCenter – Port 902 is not required if proxy mode feature turn on
445TCPConverter Standalone serverpowered-on source machineRequired for system conversion. Not required if the source computer uses NetBIOS
9089TCPConverter Standalone serverpowered-on source machineRequired for system conversion. Remote agent deployment

To perform P2V or V2V migration using VMware Converter Standalone, Launch the VMware vCenter Converter Standalone client. Click on “Convert Machine”

Step 1: Select source machine

Choose Powered on machine as source type. After that specify the IP address or name, server credentials and OS Family.

Step 2: Deploy VMware Converter standalone agent

VMware Converter will install “VMware Converter standalone agent” on the remote windows machine. You can choose one of the options for uninstalling Converter agent. I have chosen “automatically uninstall the files when import succeeds.”

Step 3: Specify the destination.

If the destination ESXi is managed by vCenter, specify the vCenter name or IP. Otherwise, specify the ESXi name or IP address. In my environment, I’m connecting to vCenter.

Step 4: Choose the destination VM folder or datacenter

Step 5: Choose the destination ESXi host or cluster, Datastore and VM Version

Next screen, you will see the current configuration. To edit the parameters, just click on Edit option.

Steps 5: Edit Destination volume

In my environment, i have multiple partition on one harddisk. I want to make each partition has one VMDK. To do it, just click on Add Disk and move the partition to different VMDK disk or you can even add new disks to converter VM’s during the conversion.

Step 6: Select VM Port Group

Final steps: Review all the Conversion parameters and click Finish button

Once the Conversion started, VMware converter Client will display the progress of the conversion job. Based on the amount of data and network transfer speed. The client will display the Estimated time to convert the virtual machine.

Leave a Reply

Your email address will not be published. Required fields are marked *