Vmware Standalone Converter Unable To Query The Live Linux Source Machine Full Hot! Link
The error "Unable to query the live Linux source machine" in VMware vCenter Converter Standalone typically occurs when the tool fails to collect system information from the source Linux OS. This is often due to restrictive shell environments, incorrect permissions, or specific disk configurations that break the tool's analysis script. Common Causes and Resolutions
Incompatible Shell Scripting (.bashrc Echo):If the source user's .bashrc file (especially for the root user) contains echo commands or other interactive output, it can interfere with the data the Converter expects to receive via SSH.
Fix: Edit /root/.bashrc (or the relevant user's file) and comment out any lines starting with echo by adding a # before them.
Sudo and Permission Requirements:The Converter needs to execute commands with root privileges. If using a non-root user, that user must be able to run sudo without a password prompt.
Fix: Use visudo to add user1 ALL=(ALL) NOPASSWD: ALL (replace user1 with your username) to the end of the /etc/sudoers file. The error "Unable to query the live Linux
Fix: Alternatively, enable the useSudo flag in converter-worker.xml located in %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\ on the Windows machine.
Duplicate or Complex Mount Points:Converter Standalone may fail if a single block device is mounted multiple times or if there are non-unique mount points, which breaks the volume analysis.
Fix: Unmount any duplicate mounts of the same device (e.g., if /dev/sda5 is mounted in two different locations) before starting the conversion.
SSH and Shell Configuration:The user assigned must have a functional shell prompt, typically /bin/bash. If that fixes the issue, create a policy
Fix: Ensure the user is assigned /bin/bash instead of /sbin/nologin in the /etc/passwd file.
Fix: Verify that SSH is running and that you can manually ssh localhost on the source machine using the same credentials entered into the Converter.
Network and Firewall Blocking:Communication between the Converter server and the Linux source requires specific ports to be open.
Fix: Ensure ports 22 (SSH), 443, and 9089 are open for bidirectional traffic. or newer versions of XFS/ext4 features)
Fix: Disable Windows UAC on the system running the Converter and run the application as an Administrator. Advanced Troubleshooting
Step B: Enable Root Login
Find the PermitRootLogin directive. It is often set to prohibit-password or no. Change it to yes.
PermitRootLogin yes
4. Disable SELinux Temporarily (for testing)
setenforce 0
If that fixes the issue, create a policy or set SELinux to permissive.
For AppArmor (Ubuntu/Debian):
systemctl stop apparmor
5. Verify Supported Filesystems
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.
- Run
df -Thto see your filesystem types. - If you are using Btrfs or ZFS, standard VMware Converter usually fails. You may need to use a different backup/restore method or a third-party P2V tool.
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. |