Description of problem:
Viewing the consoles of remote guests (i.e. guests on remote hosts) fails using VNC over TLS.  In the user virt-manager.log, the messages are:

[Sun, 26 Aug 2012 17:16:31 virt-manager 4914] DEBUG (console:1116) Starting connect process for proto=vnc trans=tls connhost=mangrove connuser=kauri connport=None gaddr=127.0.0.1 gport=5902 gsocket=None
[Sun, 26 Aug 2012 17:16:31 virt-manager 4914] DEBUG (console:412) VNC connection to 127.0.0.1:5902
[Sun, 26 Aug 2012 17:16:31 virt-manager 4914] DEBUG (console:1001) Viewer disconnected

Here, mangrove is a resolvable remote host running a valid libvirtd service over TLS, and kauri is the local machine.  The log shows that gaddr is loopback - this is wrong as the gport is the correct remote port (i.e. on remote mangrove not on localhost).

Note, these same VNC/TLS connections (and certificates) worked on fc16.


Version-Release number of selected component (if applicable):
virt-manager-0.9.4-1.fc17.noarch
virt-manager-common-0.9.4-1.fc17.noarch


How reproducible:
always

Steps to Reproduce:
1. start virt-manager
2. make a connection to remote server
3. open a console on one of the remote guests
  
Actual results:
console reports failed connection

Expected results:
the console should be shown, via VNC/TLS

Additional info:

I have fixed the behaviour by editing /usr/share/virt-manager/virtManager/console.py 
(i.e. remote access to consoles over VNC/TLS now works for me).
However, I do not know the code and I am not a programmer, so would appreciate a more knowledgeable solution.

method get_conn_host() in class ConnectionInfo (line 81 of console.py)

def get_conn_host(self):
  host = self._connhost
  port = self._connport

  if not self.need_tunnel():
    port = self.gport
    if self.gaddr != "0.0.0.0":
      host = self.gaddr

VNC/TLS is not a tunnel, and host is being set to loopback.  Commenting out or changing the last "if" so as it fails, solves the problem for me.