Hide Forgot
Description of problem: If by accident instead of supplying the url of an ESX host, the url of the Virtualcenter is passed, the error message is unclear and the debug options are none. Version-Release number of selected component (if applicable): virt-v2v-0.8.3-5.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Run the command: virt-v2v -ic esx://myhost.net/?no_verify=1 -o rhev -os rhevhost:/EXPORTS --network rhevm aldone8 Actual results: virt-v2v: Failed to connect to esx://myhost.net/?no_verify=1: libvirt error code: 8 , message invalid argument: Path has to specify the host system Expected results: Error, unable to connect to esx://myhost.net/?no_verify=1: The specified host system doesn't appear to be an ESX hypervisor host (maybe you're trying to connect to the VirtualCenter instead?)
Reassigning to libvirt as this is a libvirt error message.
Hi, I can not reproduce the bug with: libvirt-0.9.9-1.el6.x86_64 virt-v2v-0.8.3-5.el6.x86_64 # virt-v2v -ic esx://10.66.6.48/?no_verify=1 -o rhev -os 10.66.90.115:/vol/v2v_auto/nfs_export -n rhevm test virt-v2v: Failed to connect to esx://10.66.6.48/?no_verify=1: libvirt error code: 1, message: internal error 10.66.6.48 is neither an ESX 3.5, 4.x nor 5.x host What's your libvirt version?thanks!
I think the error message displayed in comment 3 is a great improvement. I do think the suggestion in the BZ description is helpful though, so I would add "(maybe you're trying to connect to the VirtualCenter instead?)" unless everybody feels that's unnecessary verbosity.
The error message is in two parts, "Failed to connect to esx://10.66.6.48/?no_verify=1" is from virt-v2v, the second part is the real reason for the failure that is from libvirt. I think the friendly warning(mentioned comment 7) should be better from upper tools rather than libvirt. But there are the case where the error is really caused by the failure of connection to ESX server, in this situation the friendly warning is not so good. any idea?
Agreed that there are cases in which the user really is trying to connect to something that isn't an ESX host or VirtualCenter, but that's why it says *maybe* you're trying...
The current error message is pretty clear already, and I asked QE team, they are satisfied with the error message, so close it.
(In reply to comment #13) > The current error message is pretty clear already, and I asked QE team, they > are satisfied with the error message, so close it. Ok, that satisfies my question in comment 7.