VMware Cloud Community
lightxx
Contributor
Contributor
Jump to solution

Unable to obtain hardware information for the selected machine error

ok. i tried every (stand alone) converter version from 4.xx to 5.0 with the same result. what i want to do is to convert a Win 2k8 R2 x64 VM residing on one of our ESXi servers.

all i get is "[07240 error 'wizardController'] Cannot query source HW info: vmodl.fault.SystemError" in the converter-gui log.

i tried all the tricks i found on the forums (cloning the VM, clean shutdown, changing the guest OS version, ....) to no avail. i simply can't get converter to work, no matter the version.

any ideas?

thanks,

tom

0 Kudos
1 Solution

Accepted Solutions
POCEH
VMware Employee
VMware Employee
Jump to solution

Is your data store name ds3@vmdk03? If so, try to remove '@' from data store name and then the conversion.

View solution in original post

0 Kudos
12 Replies
POCEH
VMware Employee
VMware Employee
Jump to solution

Please attach the logs for investigation.

0 Kudos
lightxx
Contributor
Contributor
Jump to solution

here you go ...

0 Kudos
patanassov
VMware Employee
VMware Employee
Jump to solution

Server logs will be more usefull for that. You may collect them by choosing in "Job" menu "Export logs" or by starting the wizard and clicking on "Export diagnostic logs".

You may send them in a private message and/or clear them from sensitive info.

By the way - do you want to do a P2V or V2V conversion?

Regards,

Plamen

0 Kudos
lightxx
Contributor
Contributor
Jump to solution

i want to do a V2V conversion, which works by exporting VMs to OVFs. still, i'd like to know why converter fails.

anyways, i get tons of errors in the vmware-converter-worker-*.log files.

2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] GetManagedDiskName: Get virtual disk filebacking [ds3@vmdk03] 2k8r2_sp1_template/2k8r2_sp1_template.vmdk
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] GetManagedDiskName: ticket has empty hostname, using hostname 192.168.1.140 from connection
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] GetManagedDiskName: updating nfc port as 902
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] GetManagedDiskName: get protocol as ha-nfcssl
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] GetManagedDiskName: Get disklib file name as ha-nfcssl://[ds3@vmdk03] 2k8r2_sp1_template/2k8r2_sp1_template.vmdk@192.168.1.140:902!52 08 ea fc 57 bc b7 47-df bd c5 02 47 09 b9 75
2011-09-21T11:57:15.415+02:00 [09164 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server vmdk03] 2k8r2_sp1_template/2k8r2_sp1_template.vmdk@192.168.1.140 failed: A non-recoverable error occurred during a database lookup
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] [,0] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] [,0] Error 2338 opening disk ha-nfcssl://[ds3@vmdk03] 2k8r2_sp1_template/2k8r2_sp1_template.vmdk@192.168.1.140:902!52 08 ea fc 57 bc b7 47-df bd c5 02 47 09 b9 75.
2011-09-21T11:57:15.415+02:00 [09164 info 'Default'] [,0] Error 2338 opening disk ha-nfcssl://[ds3@vmdk03] 2k8r2_sp1_template/2k8r2_sp1_template.vmdk@192.168.1.140:902!52 08 ea fc 57 bc b7 47-df bd c5 02 47 09 b9 75.
2011-09-21T11:57:15.415+02:00 [09164 error 'Default'] [BaseDiskSetComputer::DoOpen] OpenDisks failed, mntapi error: 37410
2011-09-21T11:57:15.415+02:00 [09164 error 'Default'] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 37410 MNTAPI errorType = 2, errorCode = 2338
2011-09-21T11:57:15.416+02:00 [09164 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
2011-09-21T11:57:15.419+02:00 [09164 info 'vmomi.soapStub[28]'] Resetting stub adapter for server TCP:192.168.1.140:443 : Closed
2011-09-21T11:57:15.420+02:00 [09164 error 'Default'] Unknown exception while invoking VMOMI method queryComputerInfo

btw, dns works as supposed. also, there are no errors with our vCenter Server / ESXi servers.

0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

What's your ESX IP? seems that 192.168.1.140 is no accessable from Converter server's machine.

0 Kudos
lightxx
Contributor
Contributor
Jump to solution

192.168.1.140 is the IP of the ESXi server in question.

the converter is installed on our vCenter Server which resides on the same subnet. there are no layer 3 devices in between.

the built-in windows firewall is enabled but all outgoing connections are allowed. i tried disabling the windows firewall as well, same result.

also, the converter queries the ESXi host for VMs just fine, so i don't believe its some IP connectivity issue ...

i tried both hostnames (DNS) and IPs.

Message was edited by: lightxx

0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Could you try telnet to 192.168.1.140:902 from the Converter server's machine?

0 Kudos
lightxx
Contributor
Contributor
Jump to solution

Welcome to Microsoft Telnet Client
Escape Character is 'CTRL++'
Microsoft Telnet> open 192.168.1.140:902
Connecting To 192.168.1.140:902...Could not open connection to the host, on port
23: Connect failed
Microsoft Telnet>
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Try command "telnet 192.168.1.140 902"...

0 Kudos
lightxx
Contributor
Contributor
Jump to solution

telnet 192.168.1.140 902

220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtoco
l:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Is your data store name ds3@vmdk03? If so, try to remove '@' from data store name and then the conversion.

0 Kudos
lightxx
Contributor
Contributor
Jump to solution

dude, you're a genius.Smiley Happy:smileylaugh:

you should ask vmware for some money for finding this bug, seriously.

immediately after removing the '@'s from our datastore names it started working. somebody should have a talk with someone about that at vmware.

thanks!!!!!

0 Kudos