Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

When performing a Linux conversion you receive the error: Unable to query live Linux source machine (1009153)

Last Updated: 11/1/2023Categories: TroubleshootingTotal Views: 154423Language:
Chinese (Simplified)JapaneseEnglish

17 like this article

Subscribe to get an email
newsletter with new updates

17 people found this helpful Please provide article feedback:

Symptoms

Converter Standalone stops responding for 10 minutes while displaying Retrieving source machine information.

Converter Standalone displays this error message when you click Next on the Specify Source page:

Unable to query the live Linux source machine

In the Converter GUI log file, you see an entry similar to:

error 'wizardController'] Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

In the Converter worker log file, you see an entry similar to:

Sysinfo Query failed with error Error executing ssh client for SysinfoQuery: Command not found or is not executable: C:\Program Files\VMware\VMware vCenter Converter Standalone\plink.exe

In the Converter agent log file, you see an entry similar to:

Sysinfo Query failed with error [Converter Agent SysinfoQuery] execution of vmware-sysinfo failed; return code: 126; result: bash: ./vmware-sysinfo-lin32.sh: /bin/sh: bad interpreter: Permission denied

Resolution

You must perform both troubleshooting steps listed below. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.

Notes:

Ensure that UAC is disabled on the system so plink.exe may be executed correctly.

When running VMware vCenter Converter right-click the program and select Run as Administrator.

If you perform a corrective action in any of these steps, attempt converting the Linux source operating system again.

Verify that the Linux source operating system is accepting the ssh traffic and that the user name and password used in Converter are correct and result in a functional shell prompt.

Linux source operating system:

Open a shell prompt.

Type ssh localhost and press Enter.

Log in using the same user name and password used in the Conversion wizard.

If this does not result in a successful login, correct the problem.

Note : For more information on opening a shell prompt, see Opening a command or shell prompt (1003892) .

Converter:

Open a command prompt.

Run this command:

telnet xxxx nn

where xxxx is replaced by the host name or IP address of the Linux source operating system and nn is replaced by the port being used for SSH.

If this does not result in information being displayed, a firewall might be preventing the computer running Converter Standalone from connecting to the Linux source operating system. Correct this problem.

Confirm that the .bashrc file of the user name used for authentication does not contain an echo command.

If authenticating as root, use a text editor to edit /root/.bashrc. If authenticating as a different user, use a text editor to edit /home/user name/.bashrc, where user name is replaced by the user name being used for authentication.

If a line in the file begins with echo, either delete it or change it to #echo.

Deploy the 'sysinfo' utility in a directory that is different from /tmp.

Take a backup of the converter-worker.xml file. By default, this file is located in "C:\ProgramData\VMware\VMware vCenter Converter Standalone"

Open the converter-worker.xml file using a text editor.

Locate the tag pair <sysinfoTmpRoot></sysinfoTmpRoot>. It is located inside the <converter_agent> tag. It is commented out by default and has a value of '/root'.

Uncomment the tag and either leave its value or change it to some directory of your choice that allows running executable files in it.

Save and close the file.

Restart the VMware vCenter Converter Standalone Worker service on the machine.

Ensure that user is able to log in to the linux shell, verify that the user is assigned with /bin/bash instead of /sbin/nologin in the /etc/passwd file.

For example:

root:x:0:0:root:/root:/bin/bash

Related Information

Converter Standalone uses the SFTP protocol to copy files on the source Linux system, and SFTP fails in this attempt if there is an echo statement in the .bashrc file. This behavior can be reproduced using any standard SFTP client.

P2V conversion of a Linux virtual machine fails with the error: mkdir: cannot create directory
Linux 変換を実行すると次のエラーが発生する：ライブ Linux ソース マシンをクエリできません
执行 Linux 转换时收到错误：无法查询实时 Linux 源计算机

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Converter Standalone

VMware vCenter Converter

Related Versions:

VMware vCenter Converter Standalone 5.5.x

VMware vCenter Converter Standalone 5.1.x

VMware vCenter Converter Standalone 5.0.x

VMware vCenter Converter Standalone 4.3.x

VMware vCenter Converter Standalone 4.0.x

VMware vCenter Converter 4.2.x

VMware vCenter Converter 4.1.x

VMware vCenter Converter 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant