sudo visudo -f /etc/sudoers.d/vmware-converter # Add line: converter_user ALL=(ALL) NOPASSWD: ALL Run these commands manually and verify clean, non-interactive output:
Introduction 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: "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. Understanding the Error: Why Does It Happen? 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. sudo visudo -f /etc/sudoers
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: Failed to get disk layout
sudo bash -c '( echo "DISKLABEL=msdos" for disk in /dev/sd[a-z] /dev/hd[a-z] /dev/vd[a-z]; do [ -b "$disk" ] && sudo fdisk -l "$disk" | grep "^$disk" | while read line; do start=$(echo $line | awk "print \$2") end=$(echo $line | awk "print \$3") size=$(echo $line | awk "print \$4") echo "PARTITION: $disk,$start,$end,$size" done done ) > /tmp/vmware_disk_layout.txt' This is a direct input to Converter but helps you understand alignment. Step 2: Use the VCenter Converter Helper CLI (Advanced) The helper binary vmware-converter-helper has a diagnostic mode: Before fixing the problem, you must understand the
| Cause | Explanation | |-------|-------------| | | 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. | Phase 1: Pre-Flight Checklist (Do Not Skip) Before running the Converter, manually SSH into your Linux source machine from the same Windows machine running Converter. 1.1 Verify SSH Connectivity & Permissions ssh -v converter_user@linux_source_ip Ensure you can log in without interactive prompts. If you use a password, ensure Converter is configured to provide it; if using key-based auth, ensure the key is loaded. 1.2 Test Sudo Rights (Crucial) Converter Helper will attempt to run commands with sudo . Run:
sudo -k # Reset timestamp sudo -n fdisk -l 2>/dev/null If you receive a "sudo: a password is required" message, you must configure for the converter user: