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 Converter uses a built-in SSH client ( plink.exe ) and SFTP engine ( pscp.exe ) to connect to the source Linux machine using the specified credentials.
apt-get update && apt-get install -y perl tar gzip which
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. VMware Converter expects every source file system to
Add the following line to the end of the file (replace username with the user you are connecting with): username ALL=(ALL) NOPASSWD: ALL Use code with caution. Save and exit (Ctrl+O, Enter, Ctrl+X). 2. Verify and Fix /tmp Partition Permissions
Always use the static IP address of the source machine in the Converter wizard rather than the hostname.
user wants a long, detailed article about the VMware vCenter Converter Standalone error: "unable to query the live Linux source machine full." This error occurs when converting a live Linux physical machine to a virtual machine. I need to write a comprehensive article covering the causes and solutions. To get a good range of information, I should search for general troubleshooting guides, common causes, specific solutions related to SSH and root login, detailed steps for installing converter helper, debugging and log analysis, and a summary of best practices. A diverse set of search queries will help gather a broad spectrum of information. search results have provided a good number of official Broadcom knowledge base articles and community discussions. I need to gather detailed information from these sources to write a comprehensive article. I will open several of the most relevant results, including the Broadcom KB articles that seem to directly address the error, as well as some community posts that might offer practical troubleshooting steps. have gathered a substantial amount of information from official Broadcom KB articles and community discussions. These sources provide detailed causes and solutions for the "unable to query the live Linux source machine full" error. I will now structure the article to cover the error's definition, common causes (like SSH access, root/sudo issues, /tmp directory restrictions, network and firewall problems, OS version compatibility, and specific filesystem limitations), and a comprehensive step-by-step troubleshooting guide. The article will conclude with a summary checklist and references to official Broadcom documentation. I will now start writing the article. VMware vCenter Converter Standalone throws the error "unable to query the live Linux source machine full," it's a clear signal that the process of converting a live, powered-on Linux system has been halted at the very first hurdle. This error appears when the Converter on your Windows machine initiates a secure connection to the Linux source over SSH, but fails to retrieve the critical hardware, operating system, and volume information needed to build a successful virtual machine replica. While frustrating, this error is almost always a solvable problem arising from a few common issues. Understanding the typical causes and following a structured, methodical approach to troubleshooting will lead you to a solution. This guide is designed to walk you through that process. apt-get update && apt-get install -y perl tar
(change back after migration):
. This process involves connecting via SSH, transferring a script (typically via ), and running it with elevated privileges. Broadcom support portal 1. Permissions & Shell Requirements Passwordless Sudo : If using a non-root user, that user must be able to run without a password prompt. Use username ALL=(ALL) NOPASSWD: ALL Permit Root Login : If authenticating as root, ensure PermitRootLogin yes /etc/ssh/sshd_config Standard Shell : The user must be assigned instead of /sbin/nologin or other restricted shells in /etc/passwd Clean .bashrc : Ensure the file for the user does not contain
[Windows Converter Server] │ ├─ 1. Authenticates via SSH / SFTP ───────────────────────► [Linux Source] ├─ 2. Extracts 'sysinfo' tarball into /tmp ───────────────► (Requires Write/Exec) ├─ 3. Executes './vmware-sysinfo.sh' via plink.exe ──────► (Requires Bash Shell) └─ 4. Parses XML response from standard output ◄────────── (Fails if echo/banners pollute stdout) Save and exit (Ctrl+O, Enter, Ctrl+X)
Follow these steps in order to resolve the "unable to query" error. 1. Configure Passwordless Sudo for the User
Look for the line PermitRootLogin and change its value to yes : PermitRootLogin yes Use code with caution. Save the file and restart the SSH service:
Awarded for Excellence in Employee Empowerment
Awarded for Excellence in Organisational Effectiveness
Awarded for Excellence in Innovation
