ThisCalculator

Everyday

VMware Physical to Virtual: Create a VM from a Physical Machine

Updated · Standard formula, shown below

To create a virtual machine from a physical machine in VMware, you use the vCenter Converter Standalone tool, which copies the physical machine’s disk contents into a virtual disk file (VMDK) that VMware products can run. You install the converter on a Windows machine (or run it as a server), point it at the physical machine’s IP address, and it performs the migration while the source machine stays online. The result is a bootable VM that runs on VMware Workstation, ESXi, or Fusion without reinstalling the operating system.

What Is P2V Conversion and Why Do It

Physical-to-virtual (P2V) conversion is the process of cloning a physical server or desktop into a virtual machine. The main reasons people do this are:

  • Hardware refresh: Move an old server to new hardware without reinstalling Windows or Linux and reconfiguring every application.
  • Consolidation: Run several physical machines on one ESXi host to reduce power, cooling, and rack space.
  • Disaster recovery: Keep a virtual copy of a critical physical server that can be started quickly if the original fails.
  • Testing: Create an isolated copy of a production machine to test updates or changes safely.

VMware’s official tool for this is VMware vCenter Converter Standalone. It is free and works with most Windows and Linux operating systems. For VMware Cloud on AWS or other hybrid scenarios, the same tool applies, but the destination is a vCenter or ESXi host instead of a local workstation.

How VMware Converter Works

The converter installs a temporary agent on the source physical machine. That agent reads the disk sector by sector and streams the data over the network to the destination, where it is written into a VMDK file. Because it copies at the block level, it does not need to understand the file system or the applications installed. It also captures the partition layout, boot sector, and volume information so the resulting VM can boot on its own.

For Windows sources, the converter can optionally install VMware Tools into the new VM during the conversion, which improves network and display drivers. For Linux sources, you typically install VMware Tools or open-vm-tools after the conversion. The converter supports both online (live) conversion, where the source keeps running, and offline conversion, where you boot the source from a separate environment. Online conversion is the default and causes only a few seconds of disruption at the end when it synchronizes the final changes.

Step-by-Step: Create a VM from a Physical Machine

  1. Download and install VMware vCenter Converter Standalone on a Windows machine that can reach both the source physical machine and the destination (ESXi host or Workstation). The converter itself runs as a service.
  2. Launch the converter and click “Convert machine.” Choose “Power on” as the source type and enter the IP address or hostname of the physical machine, plus administrator credentials for Windows or root for Linux.
  3. Select the destination: Choose “VMware Infrastructure virtual machine” for ESXi, “VMware Workstation or other VMware virtual machine” for a local VMDK, or “VMware Fusion” for a Mac. For ESXi, provide the host IP, username, and password.
  4. Set the VM name and location: Give the new VM a name and choose a datastore or folder. The converter will list the source disks; select the ones you want to copy (usually the system disk and any data disks).
  5. Configure the VM hardware: You can adjust the number of CPUs, memory size, and network adapters. The converter sets defaults based on the source, but you can change them. For the disk type, choose “Thin” to save space or “Thick” for performance.
  6. Start the conversion: Review the summary and click “Finish.” The converter runs a pre-check for compatibility, then begins copying. For a large disk, this can take hours over a 1 GbE network.
  7. After completion: Power off the source physical machine (if it is a server) and power on the new VM. Install VMware Tools if the converter did not do it automatically, then verify that all services start correctly.

Choosing the Right Destination: ESXi vs Workstation vs Fusion

The destination you pick changes the output format and the workflow:

  • ESXi (vSphere): The converter sends the VMDK directly to the host or vCenter. This is the standard for server P2V. You need network access to the host’s management interface (port 443) and enough datastore space.
  • Workstation (Windows/Linux): The converter writes a local VMDK file that you can open in VMware Workstation or Player. This is useful for testing or for turning a desktop into a portable VM.
  • Fusion (macOS): The converter writes a VMDK that Fusion can open. The same VMDK also works in Workstation, so this is essentially the same as the Workstation option.

If you are converting a physical machine that is already part of a Windows domain, the new VM will have a new MAC address. This can cause problems with software licenses tied to the old hardware. You may need to re-activate Windows or re-arm the license. For Linux, the main issue is usually the network interface name changing from eth0 to ens33, which can be fixed by editing /etc/network/interfaces or using a udev rule.

Common Problems and How to Fix Them

  • “Unable to connect to the source machine”: The converter needs the source to be reachable on the network and have the right ports open. For Windows, enable File and Printer Sharing (ports 445 and 139) and ensure the admin share (C$) is accessible. For Linux, the converter uses SSH (port 22) and needs root access.
  • “The source disk is too large”: The converter copies the entire disk, not just the used space. If the source has a 2 TB disk with only 100 GB used, the VMDK will still be 2 TB (unless you choose thin provisioning, which only allocates blocks as used). You can shrink the source partition before conversion, or accept the size.
  • Windows fails to boot after conversion: This often happens because the disk controller driver is missing. The converter usually handles this by injecting the VMware storage driver, but if it fails, you can add the driver manually using a Windows recovery environment. A simpler fix is to convert with the “Install VMware Tools” option checked.
  • Linux network interface not coming up: After boot, run ip link to see the interface name, then update the network configuration file. On modern systemd-based distros, you may need to create a new netplan or systemd-networkd config.

Costs and Licensing Considerations

vCenter Converter Standalone is free, but the destination platform is not. VMware Workstation Pro and Fusion Pro are paid products, while Workstation Player is free for personal use. ESXi is free for a single host with the free license, but vCenter and advanced features require a paid subscription. The converted VM itself needs a valid operating system license. Windows licenses are tied to the hardware, so moving to a VM may require a new license or a volume license agreement. Linux distributions are generally free to clone, but commercial support contracts may have clauses about virtualized environments.

Alternatives to VMware Converter

If VMware Converter does not work for your scenario, other options exist:

  • Clonezilla: A free disk-imaging tool that can clone a physical disk to a VMDK file. You boot the source from a Clonezilla live CD and save the image, then convert it using qemu-img or VMware’s vmkfstools.
  • StarWind V2V Converter: A free tool that converts between VMDK, VHDX, and other formats. It can also convert a physical machine to a VM, but it is less automated than VMware Converter.
  • Manual reinstall: For simple workloads, reinstalling the OS and copying data may be faster and cleaner than a P2V. This avoids driver and license issues entirely.

Each method has trade-offs. VMware Converter is the most automated and reliable for Windows, while Clonezilla is more flexible for Linux and can work even when the converter cannot reach the source.

Frequently Asked Questions

Can I convert a physical machine to a VM without shutting it down?

Yes, VMware Converter supports live conversion. It takes a snapshot of the disk, copies it, and then synchronizes the changes made during the copy. The source machine only needs to be rebooted if you want to avoid any inconsistency, but for most applications the online method is safe.

Does the converted VM have the same IP address?

The converter copies the network configuration, so the VM will try to use the same IP address as the physical machine. This can cause a conflict if both are on the network at the same time. Power off the physical machine before starting the VM, or change the VM’s IP address after boot.

How long does a P2V conversion take?

It depends on the disk size and network speed. A 100 GB disk over a 1 GbE network typically takes 30–60 minutes. Larger disks or slower networks can take several hours. The converter shows a progress bar and an estimated time remaining.

Can I convert a physical machine to VMware Workstation from Linux?

Yes, the converter runs on Windows, but you can install it on a Windows VM or use a Windows machine on the network. The source can be Linux, but the converter itself must run on Windows. Alternatively, you can use Clonezilla to create an image and then convert it on a Windows machine.

What happens to the physical machine after conversion?

Nothing. The converter only reads from the source; it does not modify or delete anything. You can keep the physical machine running, shut it down, or repurpose it. The new VM is an independent copy.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.