Hide Forgot
Description of problem: when connect with remote host with # virsh -c qemu+unix://{remote ip}/system it succeeds with no error, but actually connects with local unix socket. If libvirt does not support remote unix socket connection, it should report an error. Version-Release number of selected component (if applicable): libvirt-0.8.7-13.el6.x86_64 qemu-kvm-0.12.1.2-2.150.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. virsh -c qemu+unix://{remote ip}/system 2. 3. Actual results: no error, but actually connects with local unix socket Expected results: if not support remote connection, should report an error Additional info: get from "LIBVIRT_DEBUG=1 virsh -c qemu+unix://{remote ip}/system" 18:02:57.393: 4750: debug : virConnectOpenAuth:1544 : name=qemu+unix://10.66.82.173/system, auth=0x30ba370060, flags=0 18:02:57.393: 4750: debug : do_open:1250 : name "qemu+unix://10.66.82.173/system" to URI components: scheme qemu+unix opaque (null) authority (null) server 10.66.82.173 user (null) port 0 path /system 18:02:57.393: 4750: debug : do_open:1289 : trying driver 0 (Test) ... 18:02:57.393: 4750: debug : do_open:1295 : driver 0 Test returned DECLINED 18:02:57.393: 4750: debug : do_open:1289 : trying driver 1 (ESX) ... 18:02:57.393: 4750: debug : do_open:1295 : driver 1 ESX returned DECLINED 18:02:57.393: 4750: debug : do_open:1289 : trying driver 2 (remote) ... 18:02:57.393: 4750: debug : doRemoteOpen:580 : proceeding with name = qemu:///system
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Moving to POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-August/msg00672.html
Verify pass on qemu-kvm-0.12.1.2-2.185.el6.x86_64 kernel-2.6.32-193.el6.x86_64 libvirt-0.9.4-10.el6.x86_64 # virsh -c qemu+unix://10.66.4.196/system error: invalid argument: using unix socket and remote server '10.66.4.196' is not supported. error: failed to connect to the hypervisor
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1513.html