Converter Standalone for Windows runs as 64-bit, but it tries to deploy the appropriate agent (32-bit vs 64-bit) based on the source machine’s uname -m. If the source reports i686 but actually has a 64-bit kernel, or vice versa, the agent may crash.
Check:
uname -m on source Linux.
If x86_64, agent should be 64-bit. If i386/i686, agent should be 32-bit. In mixed environments, force the agent architecture by editing the Converter XML job file (advanced).
StarWind V2V Converter (free) has better Linux live conversion support. Install it on a Windows machine, connect via SSH to the Linux source, and it often succeeds where VMware Converter fails, especially with LVM and odd partition tables.
Download StarWind V2V Converter
VMware vCenter Converter Standalone is a powerful, free tool used by system administrators worldwide to convert physical machines (P2V), virtual machines (V2V), and even cloud instances into VMware virtual disks (.vmdk). However, when working with Linux source machines, a notoriously frustrating error often halts the process: Converter Standalone for Windows runs as 64-bit, but
"Unable to query the live Linux source machine." (Often accompanied by a sub-message: "Unable to retrieve disk information from the source machine. Check that the converter helper (
vmware-converter-helper) is installed and running... Failed to get disk layout.")
In severe cases—especially on heavily customized, older, or minimal Linux distributions—the conversion fails completely early in the task creation phase. This article provides a deep-dive, step-by-step methodology to diagnose, resolve, and successfully convert a live Linux machine despite this error.
If all else fails:
Converter Standalone relies on certain standard Linux utilities to query system information. If missing, the agent cannot complete its inventory. VMware vCenter Converter Standalone is a powerful, free
Required tools:
Diagnostic:
Manually run typical discovery commands over SSH:
ssh root@<source_linux_ip> "sfdisk -l 2>/dev/null || fdisk -l"
ssh root@<source_linux_ip> "blkid"
ssh root@<source_linux_ip> "lsblk -f"
If any of these return command not found, install the missing package (e.g., util-linux, lvm2, blkid from libblkid).
Before fixing the problem, you must understand the technical reality: VMware Converter Standalone is Windows-centric. It uses a helper agent (vmware-converter-helper) pushed to the Linux source over SSH. This agent attempts to execute a series of Linux commands (e.g., fdisk, lvm, df, mount) to build a block-level map of the disk. "Unable to query the live Linux source machine
The full error—"unable to query the live Linux source machine"—typically means the Converter client (running on Windows) received incomplete, malformed, or empty output from the Linux source. Common root causes include:
| Cause | Explanation |
|-------|-------------|
| Missing required binaries | fdisk, lsblk, lvm, sfdisk, partx are not in $PATH or missing. |
| Shell profile interference | The user’s .bashrc, .profile, or .cshrc echoes extraneous text (e.g., fortune, motd, echo statements) corrupting the machine-readable output. |
| LVM Volume Group naming conflicts | Duplicate VG names, missing device-mapper, or inactive logical volumes. |
| BusyBox or embedded Linux | Minimal environments (e.g., rescue systems, embedded distros) lack full GNU utilities. |
| sudo/root restrictions | The SSH user lacks passwordless sudo for critical tools. |
| Corrupted partition table | GPT vs. MBR inconsistencies or orphaned LVM metadata. |
If the Linux source uses a filesystem that the Converter version does not recognize (such as Btrfs, ZFS, or newer versions of XFS/ext4 features), it may fail to "query" the disk layout and throw a generic error.