Bug 805005

Summary:	vdagent is killed when client is connect to window 7 vm during startup on WAN (mouse doesn't work)
Product:	Red Hat Enterprise Linux 8	Reporter:	Chris Pelland <cpelland>
Component:	spice-vdagent-win	Assignee:	Arnon Gilboa <agilboa>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	acathrow, cpelland, dblechte, mkrcmari, pvine, sgordon, tdosek, uril, yhalperi
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Windows
Whiteboard:
Fixed In Version:	vdagent-win-0.1-10	Doc Type:	Bug Fix
Doc Text:	When connecting to a Windows 7 guest under WAN conditions the vdagent did not restart within the allocated timeout period of 3 seconds. This prevented the guest's mouse from responding to user input. An update has been made to ensure that the vdagent starts correctly to accept new session connections. As a result the guest's mouse will now respond correctly to user input under WAN conditions.	Story Points:	---
Clone Of:	750037	Environment:
Last Closed:	2012-04-18 18:21:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	750037
Bug Blocks:

Description Chris Pelland 2012-03-20 12:28:29 UTC

+++ This bug was initially created as a clone of Bug #750037 +++

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.

--- Additional comment from yhalperi on 2011-10-30 05:34:15 EDT ---

Created attachment 530821 [details]
vdservice log

--- Additional comment from yhalperi on 2011-10-30 05:34:39 EDT ---

Created attachment 530822 [details]
vdagent log

--- Additional comment from agilboa on 2011-11-21 05:25:54 EST ---

Created attachment 534756 [details]
fix vdagent connection & termination handling

--- Additional comment from agilboa on 2011-11-22 08:12:05 EST ---

This patch solves agent crash, and it's not risky from other perspectives.
Proposing to rhevm‑3.0.0.

--- Additional comment from mkrcmari on 2011-11-29 10:43:35 EST ---

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.

--- Additional comment from uril on 2012-01-02 10:49:42 EST ---

A Patch is available:
http://lists.freedesktop.org/archives/spice-devel/2011-December/006526.html

Comment 2 Tomas Dosek 2012-04-10 13:20:39 UTC

RHEV-toolsSetup_3.0_37.iso
rhevm-userportal-3.0.3_0001-3.el6.x86_64

While trying to reproduce above specified scenario (with 100 Kbps bandwidth using WANem) no problem in spice connection was found.  Key shortcuts (CTRL+C, CTRL+V, etc.) work fine same as mouse behaviour. Vdagent is running.

Comment 4 Stephen Gordon 2012-04-16 14:51:32 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When connecting to a Windows 7 guest under WAN conditions the vdagent did not restart within the allocated timeout period of 3 seconds. This prevented the guest's mouse from responding to user input. An update has been made to ensure that the vdagent starts correctly to accept new session connections. As a result the guest's mouse will now respond correctly to user input under WAN conditions.

Comment 6 errata-xmlrpc 2012-04-18 18:21:59 UTC

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-0494.html