On 02/11/2013 09:47 AM, Cole Robinson wrote:
Seems to work for me. I'd run virt-manager --debug and see if
traceback in the logs. Also post your VM XML.
Well, I found the proximate cause:
2013-02-14 11:01:56,697 (console:1116): Starting connect process for
proto=spice trans=ssh connhost=t510.icp.selfip.net
connport=None gaddr=0.0.0.0 gport=5900 gsocket=None
2013-02-14 11:01:56,698 (console:532): spice uri:
(virt-manager:14991): GSpice-WARNING **: Could not connect to
: No route to host
So it's failing because iptables is blocking port 5900.
This seems wrong, however. Shouldn't the SPICE connection be going over
the same SSH tunnel as libvirt?
Ian Pilcher arequipeno(a)gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.