<mclasen> so, why does virt-manager refuse to connect to a session instance <mclasen> with the words 'Cannot read CA certificate '/etc/pki/CA/cacert.pem' ? <halfline> mclasen_: http://wiki.libvirt.org/page/TLSCreateCACert mentions mv cacert.pem /etc/pki/CA <halfline> mclasen_: could it be you did qemu://localhost/session instead of qemu:///session ? <mclasen_> I am clicking on a 'session (QEMU) <mclasen_> ' in the virt-manager ui <mclasen_> which claims to be qemu:///session <halfline> okay crobinso might have a clue <crobinso> mclasen_: where's the rest of the conversation? <halfline> crobinso: we figured it out <halfline> wrong number of slashes <halfline> crobinso: if you do virt-manager -c qemu://session instead of virt-manager -c qemu:///session it gives a really confusing error message about TLS ca certificates <crobinso> halfline: ah yeah, that's some libvirt weirdness that hits people on occasion. it should be fixable if someone wanted to file a bug
To clarify a bit: # virsh --connect qemu://session error: failed to connect to the hypervisor error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory There have been quite a few people over the years that have made a similar mistake and been completely confused by the error message, it would be nice to help them out: "are you missing a slash?" or something similar.
I sent a patch upstream: http://www.redhat.com/archives/libvir-list/2016-April/msg01169.html
Upstream now: commit 0d1579572a864c33621da4d01408f8bcb6de5d4a Author: Cole Robinson <crobinso> Date: Sat Apr 16 08:59:08 2016 -0400 Explicitly error on uri=qemu://system