RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 722980 - Spice vdagent stops to respond
Summary: Spice vdagent stops to respond
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Arnon Gilboa
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-18 17:00 UTC by Marian Krcmarik
Modified: 2019-10-10 14:25 UTC (History)
10 users (show)

Fixed In Version: vdagent-win-0.1-7
Doc Type: Bug Fix
Doc Text:
Previously, using the SPICE agent on Windows 7 guests could result in unexpected behavior, such as some features of the agent not working. This was caused by a bug in the VDService agent where services would be run in a different thread than the main service thread, which resulted in a race condition. The agent has been updated and services are now run in the main service thread, so the agent performs as expected.
Clone Of:
Environment:
Last Closed: 2011-12-15 15:36:59 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1818 0 normal SHIPPED_LIVE Windows Guest Tools bug fix and enhancement update 2011-12-15 20:35:23 UTC

Description Marian Krcmarik 2011-07-18 17:00:01 UTC 
Description of problem:
Spice vdagent stops to respond even it is running and that's why It's not possible to connect to a guest from User portal - vdagent timeout error.
RHEV Spice Agent service is running and functional then after while still running but stops to work in direction agent -> client.

Version-Release number of selected component (if applicable):
Windows7 (32/64bit) guest with vdagent-win-0.1-6 and qxl-win-0.1-6
RHEVM3.0 (ic130.1)
Host: RHEL6.1 (spice-server-0.8.0-1, qemu-kvm-0.12.1.2-2.169)
Client: RHEL6.2 (spice-client-0.8.0-2)

How reproducible:
often

Steps to Reproduce:
1. Connect to Windows guest with vdagent installed and running from User portal of RHEVM3.0 (Mostly It opens correctly in full-screen after fresh start)
2. Repeat the step 1 until connection fails till vdagent timeout
  
Actual results:
spice vdagent is not working in direction agent -> client, service is running

Expected results:
spice vdagent should be responsive.

Additional info:
Comment 3 Marian Krcmarik 2011-07-18 17:13:25 UTC 
Note: Power Management was set to never sleep and turn off display.
      Shutdown and start of guest will make vdagent working again.
Comment 5 Arnon Gilboa 2011-07-20 07:45:37 UTC 
Are we sure it's win7-only issue? please try to repro on xp.

(In reply to comment #0)
> Description of problem:
> Spice vdagent stops to respond even it is running and that's why It's not
> possible to connect to a guest from User portal - vdagent timeout error.
> RHEV Spice Agent service is running and functional then after while still
> running but stops to work in direction agent -> client.
> 
> Version-Release number of selected component (if applicable):
> Windows7 (32/64bit) guest with vdagent-win-0.1-6 and qxl-win-0.1-6
> RHEVM3.0 (ic130.1)
> Host: RHEL6.1 (spice-server-0.8.0-1, qemu-kvm-0.12.1.2-2.169)
> Client: RHEL6.2 (spice-client-0.8.0-2)
Comment 6 Marian Krcmarik 2011-07-20 20:13:53 UTC 
(In reply to comment #5)
> Are we sure it's win7-only issue? please try to repro on xp.
> 
> (In reply to comment #0)
> > Description of problem:
> > Spice vdagent stops to respond even it is running and that's why It's not
> > possible to connect to a guest from User portal - vdagent timeout error.
> > RHEV Spice Agent service is running and functional then after while still
> > running but stops to work in direction agent -> client.
> > 
> > Version-Release number of selected component (if applicable):
> > Windows7 (32/64bit) guest with vdagent-win-0.1-6 and qxl-win-0.1-6
> > RHEVM3.0 (ic130.1)
> > Host: RHEL6.1 (spice-server-0.8.0-1, qemu-kvm-0.12.1.2-2.169)
> > Client: RHEL6.2 (spice-client-0.8.0-2)

Nope, I am not sure. I am just not able to reproduce that on WinXP and as Swapna mentioned during meeting she had not been as well.
I can get vdagent non-responsive on WinXP guest but only during migration and It looks differently since agent is not working in both direction and that's why I filed separated bug, pls see: https://bugzilla.redhat.com/show_bug.cgi?id=723699.
But as well I cannot be 100% sure, especially in current situation when many bugs are involved in testing.
Of course, If I reproduce on WinXP, I will let you know immediately.
Comment 7 Arnon Gilboa 2011-07-27 15:19:04 UTC 
See https://bugzilla.redhat.com/show_bug.cgi?id=719140#c11
Comment 8 Michal Haško 2011-08-04 08:37:28 UTC 
Doesn't happen to me anymore on Win7x32 guest -> changing to VERIFIED
Comment 9 Kate Grainger 2011-12-12 01:20:59 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:
Previously, using the SPICE agent on Windows 7 guests could result in unexpected behavior, such as some features of the agent not working. This was caused by a bug in the VDService agent where services would be run in a different thread than the main service thread, which resulted in a race condition. The agent has been updated and services are now run in the main service thread, so the agent performs as expected.
Comment 10 errata-xmlrpc 2011-12-15 15:36: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-2011-1818.html
Note You need to log in before you can comment on or make changes to this bug.