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
Is your data store name ds3@vmdk03? If so, try to remove '@' from data store name and then the conversion.
Please attach the logs for investigation.
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
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.
btw, dns works as supposed. also, there are no errors with our vCenter Server / ESXi servers.
What's your ESX IP? seems that 192.168.1.140 is no accessable from Converter server's machine.
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
Could you try telnet to 192.168.1.140:902 from the Converter server's machine?
Try command "telnet 192.168.1.140 902"...
telnet 192.168.1.140 902
Is your data store name ds3@vmdk03? If so, try to remove '@' from data store name and then the conversion.
dude, you're a genius.: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!!!!!