On 02/14/2013 12:06 PM, Ian Pilcher wrote:
On 02/11/2013 09:47 AM, Cole Robinson wrote:
Seems to work for me. I'd run virt-manager --debug and see if there's any 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 connuser=root connport=None gaddr=0.0.0.0 gport=5900 gsocket=None
2013-02-14 11:01:56,698 (console:532): spice uri: spice://t510.icp.selfip.net?port=5900
(virt-manager:14991): GSpice-WARNING **: Could not connect to t510.icp.selfip.net: 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?
virt-manager doens't use the SSH tunnel if you have the listen address configured to 0.0.0.0, as that debug line above indicated (gaddr=0.0.0.0). Reset it to the default of 127.0.0.1 and virt-manager will do what you want.
- Cole