On 04/19/2016 03:59 AM, Maxim Nestratov wrote:
19.04.2016 2:04, Cole Robinson пишет:
It's a fairly common error that a user tries to connect to a URI like qemu://system or qemu://session (missing a slash). This errors like:
$ virsh --connect qemu://session error: failed to connect to the hypervisor error: Unable to resolve address 'session' service '16514': No address associated with hostname
If you already know that the standard qemu URI has 3 slashes, that error will make it obvious enough. But new user's may not get it. There's even a RHEL support page explicitly mentioning it!:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/htm...
Catch this error early in libvirt.c virConnectOpen for qemu (and vbox which has similar rules
Please, add 'vz' also as it suffers from the problem too. Though it doesn't support vz:///session it clearly says about it in the error message.
Sounds good, I'll send a v2 - Cole