Troubleshooting VMware Converter: "Unable to Query the Live Linux Source Machine"
Running into the dreaded "Unable to query the live Linux source machine" error while attempting a Physical-to-Virtual (P2V) or Virtual-to-Virtual (V2V) migration using VMware vCenter Converter Standalone can bring your migration project to a screeching halt.
This specific error triggers when the Converter fails to properly gather hardware and volume configuration details from your powered-on Linux system.
Let's break down the most common culprits and how to bypass them. 🔍 The Big Three Causes
When this error pops up, the logs usually point to one of these three architectural or security bottlenecks: 1. The Multi-Mount Conflict
This is arguably the most common cause documented in the Broadcom Knowledge Base.
The Problem: VMware Converter expects every source file system to map to a single, unique mount point. If you have a single disk device mounted in multiple directories (like a disk bound to / and at the same time to a directory under /var), the partition analysis logic breaks.
The Clue: Look at your vmware-converter-worker.log for a line saying: No disks for volume with id '/dev/...' and label.
The Fix: Temporarily umount the secondary mount points on your Linux machine until the initial query and cloning task completes. 2. Sudo Without Password Prompting
To pull raw hardware and disk layouts, the Converter executes commands via SSH using administrative permissions.
The Problem: If you aren't logging directly in as root and are instead using a standard user with sudo privileges, Converter will fail if sudo asks for an interactive password prompt.
The Fix: Grant your conversion user passwordless sudo access. Run visudo on the Linux source and append:your_username ALL=(ALL) NOPASSWD: ALL 3. Blocked Executables in /tmp
VMware Converter executes its helper queries by deploying a sysinfo tarball package to the source system's /tmp directory and executing a script. Troubleshooting VMware Converter: "Unable to Query the Live
The Problem: Many security-hardened Linux environments mount the /tmp directory with the noexec permission flag. This hardens the server but stops the script right in its tracks with a "Permission denied" error.
The Fix: You can either temporarily remount /tmp with execution rights using mount -o remount,rw,exec /tmp or change the target path by editing the converter-worker.xml file on the Windows machine hosting the Converter software to point to another writable directory. 🛠 Quick Troubleshooting Checklist
If none of those big three solved your issue, check off these foundational basics:
🔐 Check .bashrc for echoes: If the user profile logs in and returns an interactive text string (like a welcome banner or an echo command in .bashrc), it confuses the SFTP transfer mechanism used by the tool. Move echoes to .bash_profile.
🔌 Network & SSH Ports: Ensure that ports 9089 and 443 are reachable, and verify that standard SSH port 22 is fully accepting connections from your Converter machine.
🔢 SSHD Ciphers/HMACs: Older versions of Converter rely on standard, sometimes deprecated algorithms like hmac-sha1. If your Linux server strictly demands newer SHA2 algorithms, Converter may fail to authenticate.
💿 Unsupported RAID: Remember that the standalone converter does not support native Software RAID (MDRAID) setups.
Are you still getting blocked by hardware queries on your specific Linux distro? Drop your log snippet below and let's figure it out!
The error "Unable to query the live Linux source machine" in VMware vCenter Converter Standalone typically occurs during the initial source discovery phase when the Converter agent fails to collect hardware and system information from the Linux machine. 1. Verify SSH and Authentication
The Converter communicates with Linux sources via SSH. Ensure the following configurations are met:
Root Login: Ensure PermitRootLogin yes is set in the source machine's /etc/ssh/sshd_config. Restart the SSH service after changes (systemctl restart ssh).
Bash Shell: The user account must be assigned /bin/bash in /etc/passwd. Accounts with /sbin/nologin will fail. Look for "Permission denied" (indicates sudo/root issues)
Passwordless Sudo: If not using the root account, the provided user must have sudo privileges without a password prompt for all commands. Add the user to /etc/sudoers using visudo: username ALL=(ALL) NOPASSWD: ALL. 2. Clean Up Login Scripts (.bashrc)
Interactive login scripts that produce output (like echo commands or banners) can break the Converter's automated SSH session.
Check /root/.bashrc (or the specific user's home directory) and comment out any echo lines or script calls that generate text upon login. 3. Fix Temporary Directory Permissions
Here’s a detailed content piece covering the error “VMware Standalone Converter unable to query the live Linux source machine (full)” , including causes, symptoms, and step-by-step solutions.
If the above steps fail, the logs will reveal the exact command that is failing.
On the Linux Source Machine:
Look at the system logs or the specific converter logs located typically at:
/var/log/vmware-vcenter-converter-standalone-agent/converter-agent.log
On the Windows Converter Machine:
Check the Worker logs:
C:\ProgramData\VMware\VMware vCenter Converter Standalone\Logs\converter-worker.log
What to look for:
Converter Standalone uses SSH to connect to the Linux source and deploy the agent. Even if you provide valid root credentials, subtle SSH issues can block the query.
Check:
systemctl status sshd or service ssh statusPermitRootLogin yes in /etc/ssh/sshd_config)ssh -v root@<source_linux_ip>To maximize your chances of success, run these commands on the Linux machine before starting the conversion wizard:
# 1. Stop firewall
systemctl stop firewalld 2>/dev/null || ufw disable 2>/dev/null || service iptables stop 2>/dev/null
# 2. Disable SELinux
setenforce 0
# 3. Ensure SSH is running
systemctl restart sshd
# 4. Clean up old agent attempts
rm -rf /usr/lib/vmware-vcenter-converter-standalone-agent
VMware Standalone Converter Unable to Query the Live Linux Source Machine: A Comprehensive Guide If all else fails
The VMware Standalone Converter is a popular tool used to convert physical machines to virtual machines (VMs) in a matter of minutes. However, users may sometimes encounter issues during the conversion process. One common error that arises is the inability to query the live Linux source machine. In this article, we will explore the reasons behind this error and provide a step-by-step guide on how to resolve it.
What is VMware Standalone Converter?
The VMware Standalone Converter is a software tool developed by VMware that allows users to convert physical machines to VMs. It supports a wide range of source machines, including Windows and Linux systems, and can convert them to VMware VMs. The tool is particularly useful for organizations that want to migrate their existing infrastructure to a virtualized environment.
Understanding the Error: Unable to Query the Live Linux Source Machine
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:
Troubleshooting Steps
To resolve the error, follow these troubleshooting steps:
Converter needs a password or an SSH key for root. Many modern Linux distros disable password-based root SSH by default.
Temporarily enable root password SSH (change back after migration):
sudo sed -i 's/#PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config
sudo systemctl restart sshd
Security tip: Use a strong temporary password and disable root SSH after P2V.
sudo e2fsck -f /dev/mapper/vg_name-lv_name # For ext filesystems
sudo lvchange --refresh vg_name/lv_name
Converter expects a POSIX-compliant shell (like bash or sh). If the source Linux machine uses a limited shell (e.g., rbash, dash with restricted mode), or if .bashrc/.profile scripts produce interactive output, the remote command execution can fail.
Check:
bash or shecho $SHELLssh root@<source_linux_ip> "ls /tmp"If all else fails, consider:
Would you like a one-page checklist or a script to run on the Linux source to auto-fix common issues?