Testing some combinations - using a quantal server, a quantal client can do virsh -c qemu+tls://guest/server list just fine. A precise client usually works, but occasionally gives a warning as shown below. (Will try a precise server now, as I believe that's the real problem)
ubuntu@server-17191:~$ virsh -c qemu+tls://10.55.60.186/session list
Id Name State
----------------------------------
ubuntu@server-17191:~$ virsh -c qemu+tls://10.55.60.186/session list
Id Name State
----------------------------------
ubuntu@server-17191:~$ virsh -c qemu+tls://10.55.60.186/session list
Id Name State
----------------------------------
2012-09-27 16:24:33.223+0000: 18600: info : libvirt version: 0.9.8
2012-09-27 16:24:33.223+0000: 18600: warning : virNetClientIncomingEvent:1660 : Something went wrong during async message processing
Testing some combinations - using a quantal server, a quantal client can do virsh -c qemu+tls: //guest/ server list just fine. A precise client usually works, but occasionally gives a warning as shown below. (Will try a precise server now, as I believe that's the real problem)
ubuntu@ server- 17191:~ $ virsh -c qemu+tls: //10.55. 60.186/ session list ------- ------- ------- ------
Id Name State
-------
ubuntu@ server- 17191:~ $ virsh -c qemu+tls: //10.55. 60.186/ session list ------- ------- ------- ------
Id Name State
-------
ubuntu@ server- 17191:~ $ virsh -c qemu+tls: //10.55. 60.186/ session list ------- ------- ------- ------
Id Name State
-------
2012-09-27 16:24:33.223+0000: 18600: info : libvirt version: 0.9.8 omingEvent: 1660 : Something went wrong during async message processing
2012-09-27 16:24:33.223+0000: 18600: warning : virNetClientInc