Hide Forgot
Description of problem: Under WAN conditions (e.g., 1Mbps), I connected spice client to a Windows7 vm, during the VM startup. The mouse didn't work. Investigate it with Arnon. Both server and client are in client mouse mode. However, the agent is killed on the VM and is not restarted. From the logs we saw, that vdservice attempts to kill the vdagent after a CONNECT event (as it should). It waits 3 seconds for the vdagent to be actually killed, and then it should restart it. However, it took the agent more than 3 seconds to die, and the vdservice didn't restart it. It is not totally clear why under WAN it takes longer to kill the agent. I attached the vdservice and vdagent logs. Version-Release number of selected component (if applicable): vdagent-win-0.1-8 virtio-win-1.4.0 spice-client-0.8.2-7 spice-server-0.8.2-4 How reproducible: Steps to Reproduce: 1.Start a Windows 7 vm 2. Connect to the vm during start up, with Spice client, Under WAN Actual results: No vdagent is running. i.e., mouse clicks don't work, copy-paste don't work, etc.
Created attachment 530821 [details] vdservice log
Created attachment 530822 [details] vdagent log
Created attachment 534756 [details] fix vdagent connection & termination handling
This patch solves agent crash, and it's not risky from other perspectives. Proposing to rhevm‑3.0.0.
Switching back to ASSIGNED since the problem still occurs when connecting in early pahse of startup under WAn with low bandwith - ~100 Kbps. We (Arnon and me) tested some scratch builds to determine the right solution.
A Patch is available: http://lists.freedesktop.org/archives/spice-devel/2011-December/006526.html
Technical Notes are copied from bug 805005
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1502.html