"FAILED: A general system error occurred: getaddrinfo hostname/IPaddress: Name or service not known getaddrinfo Name or service not known Network error. Host hostname/IPaddress key can't be retrieved. (return code 2)"
C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs\vmware-converter-server-X.log
), you may see entries related to this error indicating that the hostname or IP address cannot be resolved or accessed during the conversion process.<YYYY-MM-DD>T<time>[01320 info 'vmomi.soapStub[0]'] Resetting stub adapter for server <cs p:02adef48, PIPE:\\.\pipe\vmware-converter-worker-soap> : Closed <YYYY-MM-DD>T<time>[02272 error 'Default'] [task,350] [LRO] Unexpected Exception: vmodl.fault.SystemError <YYYY-MM-DD>T<time> 142+08:00 [02272 info 'Default'] [task,379] [task-3] -- ERROR -- Convert: vmodl.fault.SystemError --> (vmodl.fault.SystemError) { --> dynamicType = <unset>, --> faultCause = (vmodl.MethodFault) null, --> reason = "Network error. Host hostname key can't be retrieved. --> (return code 2)", --> msg = "", --> }</time></time></time>
This issue occurs because the /etc/hosts.allow
file on the source Linux machine may not be configured to allow incoming connections from the machine running VMware Converter. By default, the /etc/hosts.allow
file may restrict access based on IP addresses or hostnames, preventing proper communication between the Converter and the source machine.
Resolution:
Log into the source Linux machine as root.
Backup the current /etc/hosts.allow
file to ensure you can restore it later:
Modify the /etc/hosts.allow
file to accept connections from any machine on the network:
Restart the network service to apply the changes:
Retry the P2V conversion process. It should now proceed past the 3% mark without the network-related error.
After successfully converting the machine from physical to virtual, restore the original /etc/hosts.allow
file from the backup to maintain previous security settings:
This should resolve the error and allow the P2V conversion to complete successfully.