Vmware Standalone Converter Unable To Query The Live Linux Source Machine Full Patched File

When using VMware vCenter Converter Standalone, the error "Unable to query the live Linux source machine" typically occurs because the software cannot retrieve essential hardware and system information from the source Linux machine. Common Causes and Troubleshooting Steps

Below is a guide to resolving this issue based on known technical causes and Broadcom Knowledge Base articles: 1. SSH and Terminal Environment Issues

Remove 'echo' Statements: Ensure the .bashrc or .profile files for the user account (typically root) do not contain any echo or interactive commands. These can disrupt the SFTP stream the converter uses to copy information.

Verify Shell Type: The source user should have /bin/bash as their default shell.

SSH Configuration: Ensure the SSH daemon is running and reachable on port 22. Some environments may fail if the SSH configuration uses unsupported HMACs; VMware Converter typically expects hmac-sha1 or hmac-md5. 2. File System and Execution Permissions

Unmount Duplicate Mountpoints: The converter may fail if a single disk device is mounted at multiple locations. Ensure each device has only one mountpoint in the file system. When using VMware vCenter Converter Standalone , the

Writable /tmp Directory: Ensure the /tmp directory on the source is writable and allows the execution of scripts.

Change Sysinfo Path: If /tmp is mounted with noexec, you can modify the converter-worker.xml file (located on the Windows machine running the converter) to use a different directory by uncommenting the tag and setting it to a path like /root. 3. Network and Security Settings

Linux P2V issue: unable to query the live Linux source machine

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.

---

Root Causes

| Cause | Explanation | |-------|-------------| | Insufficient permissions | SSH user lacks root or sudo privileges with NOPASSWD. | | Missing required packages | perl, tar, gzip, or which not installed. | | Shell restrictions | User has a restricted shell (e.g., /bin/rbash) or no shell access. | | Firewall or network issues | High latency, MTU mismatch, or SSH port blocked. | | Unsupported Linux distribution or kernel | Very old or too new kernels may not be supported. | | Agent installation path issues | No write access to /tmp or /root; or no space left. | | SELinux or AppArmor blocking | Security policies blocking agent execution. | Root Causes | Cause | Explanation | |-------|-------------|

Why Does This Happen?

The conversion process for a live Linux machine relies on the Converter Standalone agent being pushed to and executed on the source Linux host. This agent collects disk, partition, and OS configuration data. When the query fails, it indicates a breakdown in one or more of the following stages:

1. Agent deployment (SSH connection, authentication, or file copy issues)
2. Agent execution (missing dependencies, incompatible libraries, or architecture mismatch)
3. Communication (firewalls, port blocking, or network instability)
4. Source OS compatibility (unsupported kernel, init system, or missing tools)

Fix: VMware Converter “Unable to Query the Live Linux Source Machine”

If you’ve ever tried to convert a physical Linux server (P2V) using VMware vCenter Converter Standalone, you’ve likely hit this frustrating roadblock:

“Unable to query the live Linux source machine.”

You enter the root credentials, the network test passes, but the conversion fails immediately during the source analysis phase. Don’t worry—this is a common issue, and it’s almost always fixable.

In this post, I’ll explain why it happens and walk you through the proven fixes. If that produces clean output

Useful commands (run on source or Converter host as noted)

• Debug SSH from Converter host:
  • ssh -vvv user@source_host
• Check sshd logs (on source):
  • sudo tail -F /var/log/secure (RHEL/CentOS)
  • sudo tail -F /var/log/auth.log (Debian/Ubuntu)
• Install utilities (example for Debian/Ubuntu):
  • sudo apt-get update && sudo apt-get install -y lsof lvm2 util-linux
• Activate LVM:
  • sudo vgscan && sudo vgchange -ay
• Temporarily set SELinux permissive:
  • sudo setenforce 0

---

Common Symptoms

• The conversion task fails at 1%–2%.
• Error log shows: FAILED: Unable to query the live Linux source machine.
• Converter successfully connects via SSH but times out or returns incomplete data.
• You may also see: Unable to install the agent on the source machine.

The Fix:

Create a dedicated non-interactive profile for the converter user.

1. Log in as the converter user.
2. Edit ~/.bashrc (or equivalent) and wrap all echo statements:

# Only run if shell is interactive
if [[ $- == *i* ]]; then
    echo "Welcome"
    fortune
fi

3. Better yet: Create ~/.ssh/environment (enable PermitUserEnvironment yes in /etc/ssh/sshd_config) or instruct Converter to use a clean shell:

# Test clean invocation
ssh converter_user@linux_host "bash --noprofile --norc -c 'fdisk -l 2>/dev/null'"

If that produces clean output, configure the Converter’s advanced SSH options (if available) or set the remote shell to sudo -i or bash --noprofile --norc.

---

Detailed Resolution Steps

1. Ensure Root SSH Access with Password (or Key)

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.