The VMware P2V (physical to virtual) migration tool allows user to clone the physical system in order to apply it on a virtual machine. When using the P2V tool, the user must have two sets of system running. The first is the physical system or host which is the one being cloned and the second is the virtual machine which can be made possible through VMware workstation or server application. There are several issues that may arise when initializing the VMware P2V migration tool.
First, when the cloning protocol starts, the software may detect that the target disk has not enough space for the operation to begin. This may happen even if the target disk is large or has enough disk space. One probable solution to this issue is to allow the software to resize the target disk so that it will conform to the specification of the program. Usually, this will solve the problem and the cloning will run smoothly. However, if the program still rejects the disk after allowing it to resize the partition, then the user must terminate cloning and acquire more disk space to accommodate the operation.
Second, there are preliminary steps and systems configuration that must be carried out first before initializing cloning and migration. If these steps are not carried out the operation may hang thus terminating the operation. The preliminary steps can be found on the documentation of the P2V software.
Finally, the P2V operation copies everything from the target disk even if it contains partitions. This will result to redundant files or unwanted being copied to the clone system. This can be solved by following the procedures for handling file copy partition during cloning.