This error usually pops up immediately after you enter the credentials for your source Linux machine. It indicates that the Converter worker cannot gather the necessary hardware and configuration data from the source to build the destination VM.
Here’s a detailed content piece covering the error , including causes, symptoms, and step-by-step solutions.
The error "unable to query the live Linux source machine" typically occurs when the VMware Standalone Converter is trying to connect to a live Linux source machine. This error can be caused by several factors, including:
# Check if noexec is applied to /tmp mount | grep /tmp # Remount /tmp temporarily with executable permissions mount -o remount,rw,exec /tmp # Check for excessive directory links (ext3 limitation) ls -ld /tmp Use code with caution. This error usually pops up immediately after you
sudo /opt/vmware-converter-helper/vmware-converter-helper --debug
Unmount any stale network drives (NFS/SMB) before starting. The Converter may attempt to query these and timeout.
Ensure administrative remote shell logins are allowed if executing direct roots: PermitRootLogin yes Use code with caution. Restart the host service layer to register changes: sudo systemctl restart sshd Use code with caution. 4. Echo Statements in Shell Initialization Files ( .bashrc ) The error "unable to query the live Linux
: If your source machine uses NVMe disks or certain LVM configurations not supported by your specific Converter version, it may fail to map the drives. Broadcom support portal 3. Permission & Execution Blocks The discovery process involves running a script called vmware-sysinfo.sh directory. Unable to query live Linux source machine
: Unmount any duplicate mounts of the same device (e.g., if /dev/sda5 is mounted in two different locations) before starting the conversion.
Are the on the same subnet? Which version of VMware Converter are you running? The Converter may attempt to query these and timeout
Let's break down the most common culprits and how to bypass them. 🔍 The Big Three Causes
: Must be open from the source Linux machine to vCenter/ESXi host (crucial for the subsequent cloning phase, but good to verify early).
sudo vgchange -ay
The tool extracts and executes these binaries within the target's /tmp directory. If hardened security rules enforce a noexec flag on /tmp inside /etc/fstab , the binary payload cannot execute, throwing a permission barrier.
Look for specific Linux exit codes or SSH "Permission Denied" markers.