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.
sudo sed -i 's/#PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config sudo systemctl restart sshd
If you can provide the specific Linux distribution and version, as well as the Converter version you are using, I can offer more tailored troubleshooting steps. "unable to query the live source machine" in P2V convert
VMware vCenter Converter Standalone is a powerful tool for converting physical machines, virtual machines, and other system images into VMware virtual machines. However, when attempting to convert a live Linux source machine, administrators often encounter a frustrating roadblock: the converter fails to query the source machine. This typically manifests as an error during the "Query Source Machine" phase, with messages like: You enter the root credentials, the network test
) is mounted to multiple directories, Converter often gets confused and cannot map the volumes. Unmount any duplicate mounts before starting. Unsupported Volume Managers : Converter primarily recognizes standard partitions and
Ensure the user has a valid shell, such as /bin/bash , in the /etc/passwd file. 5. Manually Run sysinfo
This specific error triggers when the Converter fails to properly gather hardware and volume configuration details from your powered-on Linux system. "unable to query the live source machine" in
: Temporarily permit root login on the source machine.
Root Cause 2: Multiple Mount Points for a Single Disk Device
Ensure that the option Requiretty is disabled, as it prevents VMware Converter from executing non-interactive commands. Look for Defaults requiretty and comment it out with a # if it exists. 3. Missing System Prerequisites (tar, wget, SFTP) Unmount any duplicate mounts before starting
VMware Converter requires a strict 1:1 relationship between block devices and mount points. If a single disk partition or logical volume is mounted in multiple directories simultaneously (often due to Docker, cluster file systems, or administrative binds), the hardware discovery script fails.
When faced with this error, systematically run through this quick-reference checklist: