[libvirt] [PATCH v2 1/2] Explicitly error on uri=qemu://system
Cole Robinson
crobinso at redhat.com
Tue Apr 19 21:52:21 UTC 2016
On 04/19/2016 12:46 PM, Maxim Nestratov wrote:
> 19.04.2016 19:22, 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/html/Virtualization_Deployment_and_Administration_Guide/sect-Troubleshooting-Common_libvirt_errors_and_troubleshooting.html
>>
>>
>> Catch this error early in libvirt.c virConnectOpen for qemu (and vbox
>> which has similar rules
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1038304
>> ---
>> v2:
>> Use conventional function naming
>> Improve a comment
>> Handle 'vz' driver
>>
>> src/libvirt.c | 35 +++++++++++++++++++++++++++++++++++
>> 1 file changed, 35 insertions(+)
>
> ACK
>
Thanks, pushed patch this now
- Cole
More information about the libvir-list
mailing list