Hide Forgot
Description of problem: With virt-manager Always meet this followings error output . But with virsh command line won't meet the same error Unable to open a connection to the libvirt management daemon. Libvirt URI is: qemu+tls://root@dhcp-65-85/system Verify that: - The 'libvirtd' daemon has been started Version-Release number of selected component (if applicable): virt-manager-0.8.6-3.el6.noarch How reproducible: always Steps to Reproduce: 1.start virt-manager 2.click File -> Add connection 3.QEMU/KVM for hypervisor , check on "Connect to remote host" , Method TLS Username root , Hostname dhcp-65-85 Actual results: Unable to open a connection to the libvirt management daemon. Libvirt URI is: qemu+tls://root@dhcp-65-85/system Verify that: - The 'libvirtd' daemon has been started Expected results: could connect to remote host successfully via virt-manager Additional info: # virsh -c qemu+tls://dhcp-65-85/system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # quit [root@dhcp-93-106 ssl]# virsh -c qemu+tls://root@dhcp-65-85/system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # quit
Please provide the output of virt-manager --debug when reproducing this issue
Created attachment 488321 [details] virt-manager.log Failed to reproduce the problem today , but got the error message from the ~/.virt-manager for the day I reported this bug . Today , I got different "Add Connection" dialog , for there was no hostname dropdownlist available for the machines I can connect . But on 24th , I got a list for lots of available machines .
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.
Hmm, there are lot's of dbus and avahi errors in the log, and the error you got from libvirt had was a timeout error. Maybe you were having networking issues? Or some other package update was making things behave oddly? Either way, since it's working for you now, closing as WORKSFORME. If you can reproduce in the future with latest 6.1 packages, please reopen with the --debug output