Ok, I tried leaving a connection to guest with RHEL host, and I managed to caputre some debugging:
(remote-viewer:21306): GSpice-DEBUG: spice-channel.c:913 main-1:0: Read error Error receiving data: Connection timed out
(remote-viewer:21306): GSpice-CRITICAL **: recv hdr: Connection timed out
(remote-viewer:21306): GSpice-DEBUG: spice-channel.c:2136 got socket error: 25
then it closes remote-viewer
Could you open a bug?
----- Original Message -----
> The VMs are fine, in a running state. If you close the spice session (kill
> the window) and then open it again, it works fine until it is left idle
> again for about 15 minutes.
> On Wed, Sep 4, 2013 at 7:45 PM, Marc-André Lureau < mlureau redhat com >
> ----- Original Message -----
> > Hi
> > The bulk of our users run Windows XP (32 bit) clients accessing either Win
> > XP
> > or Win 7 guests. Myself and the other sys admin run Fedora 18 and Fedora 19
> > desktops respectively. We all experience the time out problem.
> > Between the client PCs (Windows and Fedora), we have a pair of firewall
> > clusters of different brands. I am the primary administrator of the "inner"
> > firewall cluster but have no visibility of the outer firewall cluster.
> > Basically we have:
> > Client PCs --- Outer FW cluster --- Inner FW cluster --- RHEV-M and RHEV-H
> > (actually fat RHEL)
> > I have ensured that the FW cluster I maintain does not do timeouts on idle
> > connections. I can ssh into a RHEL VM, and leave the SSH session idle for
> > days without a disconnect. Once I get a SPICE session to a VM, if I don't
> > use it for about 15 minutes or so, it either freezes completely (the SPICE
> > session, not the VM) or disconnects with "unable to connect to the graphic
> > server"
> Have you checked the VM are not suspended or down? (virsh list --all)
> virt-tools-list mailing list
> virt-tools-list redhat com