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 839564 - vdservice stops running inside windows guests - mouse pointer cannot click
Summary: vdservice stops running inside windows guests - mouse pointer cannot click
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Arnon Gilboa
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-12 10:15 UTC by Grant Williamson
Modified: 2019-10-10 14:19 UTC (History)
10 users (show)

Fixed In Version: vdagent-win-0.1-12
Doc Type: Bug Fix
Doc Text:
When running a Windows guest sometimes the vdservice stopped running,causing the mouse pointer to no longer click or accept input inside the guest. An update has been made to ensure that the vdagent starts correctly and these problems will no longer occur. As a result the guest's mouse will now respond correctly to user input.
Clone Of:
Environment:
Last Closed: 2012-12-04 18:17:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vdagent log (126.46 KB, text/x-log)
2012-07-12 10:15 UTC, Grant Williamson 		no flags Details
vdservice log when it has crashed. (42.61 KB, text/x-log)
2012-07-12 10:15 UTC, Grant Williamson 		no flags Details
Service not working direct after boot. (25.70 KB, text/x-log)
2012-09-04 10:33 UTC, Grant Williamson 		no flags Details
Service not working on boot. (72.08 KB, text/x-log)
2012-09-04 10:34 UTC, Grant Williamson 		no flags Details
vdservice: retry virtio-serial read on ERROR_NO_SYSTEM_RESOURCES (1450) (1018 bytes, patch)
2012-09-16 11:00 UTC, Arnon Gilboa 		no flags Details | Diff
vdservice: stop service on virtio failure (7.25 KB, patch)
2012-09-16 11:01 UTC, Arnon Gilboa 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1502 0 normal SHIPPED_LIVE new package: spice-vdagent-win 2012-12-04 23:07:17 UTC

Description Grant Williamson 2012-07-12 10:15:23 UTC 
Created attachment 597755 [details]
vdagent log

Description of problem:
When running a Windows guest sometimes the vdservice will stop running.
Causing mouse pointer to no longer click, accept input inside guest.

Version-Release number of selected component (if applicable):
RHEL 6.3
Windows 7 or Windows XP.
vdagent-win-0.1-11
spice-gtk-0.11-11
qemu-kvm-0.12.1.2-2.295

I include the log files of an instance when it has crashed.
Comment 1 Grant Williamson 2012-07-12 10:15:56 UTC 
Created attachment 597756 [details]
vdservice log when it has crashed.
Comment 3 Arnon Gilboa 2012-08-08 10:55:25 UTC 
(In reply to comment #1)
> Created attachment 597756 [details]
> vdservice log when it has crashed.

Do you always get the "OpenInputDesktop() failed: 624" on vdagent.log before vdservice stops working?

MSDN says:
624 (0x270) ERROR_DLL_INIT_FAILED_LOGOFF
{DLL Initialization Failed} The application failed to initialize because the window station is shutting down.

Is it relevant to your scenario?
Comment 4 Grant Williamson 2012-08-09 10:35:37 UTC 
Not sure, we worked around the problem by adding a auto restart on service fail.
I know from other people the problem also exists on Windows clients run on Fedora 17.
Comment 5 Arnon Gilboa 2012-08-13 12:45:06 UTC 
(In reply to comment #4)
> Not sure, we worked around the problem by adding a auto restart on service
> fail.
Workaround is not a solution. Can you easily reproduce it? what's the exact scenario?

> I know from other people the problem also exists on Windows clients run on
> Fedora 17.
I guess you meant Windows guest?
Comment 6 Grant Williamson 2012-08-27 12:02:45 UTC 
Windows Guest, yes. Windows XP 32 Bit or Windows 7 64 bit.
Install the service and at certain times, it just fails.

We have 1000's of people using the copy and paste feature of a Windows guest so a workaround was required.
Comment 7 Grant Williamson 2012-09-04 10:33:20 UTC 
Created attachment 609620 [details]
Service not working direct after boot.
Comment 8 Grant Williamson 2012-09-04 10:34:10 UTC 
Created attachment 609621 [details]
Service not working on boot.
Comment 9 Grant Williamson 2012-09-04 10:34:57 UTC 
I disabled the auto restart, rebooted the KVM 2x and here you can see the service has crashed again.
I would say it is easy to reproduce.
Comment 10 Arnon Gilboa 2012-09-10 07:40:59 UTC 
(In reply to comment #9)
> I disabled the auto restart, rebooted the KVM 2x and here you can see the
> service has crashed again.
> I would say it is easy to reproduce.

I cannot see the vdservice crash reason from logs. It seems like you don't get the OpenInputDesktop agent error, but there is a suspicious GetOverlappedResult failure (1450 = ERROR_NO_SYSTEM_RESOURCES) in vdservice, which doesn't stop the service but may give us a clue.

Which version of virtio serial drivers are you using?
Comment 11 Grant Williamson 2012-09-10 07:57:24 UTC 
Arnon, we are using this driver.

virtio-serial(vioser.inf)	07/03/2012,52.63.103.3000
Comment 12 Arnon Gilboa 2012-09-11 07:55:06 UTC 
Grant, it will be nice if we can debug it online as I cannot repro on my env.
Catch me at irc.gimp.net #spice

(In reply to comment #11)
> Arnon, we are using this driver.
> 
> virtio-serial(vioser.inf)	07/03/2012,52.63.103.3000
Comment 13 Grant Williamson 2012-09-12 06:36:32 UTC 
Arnon, will try and ping you today.

Indeed seems error 1450 does occur quite often. Sometimes when you login the log shows Service stopped.
Comment 14 Grant Williamson 2012-09-12 15:32:41 UTC 
Chatted with Arnon, outcome.

/* note: On WinXP SP3 with rhel6ga virtio-win-1.1.16 vioser drivers,
 * ENSR seems to be synonymous with when we'd normally expect
 * ERROR_HANDLE_EOF. So treat it as such. Microsoft's
 * recommendation for ERROR_NO_SYSTEM_RESOURCES is to
 * retry the read, so this happens to work out anyway. On newer
 * virtio-win driver, this seems to be replaced with EOA, so
 * handle that in the same fashion.
 */

1450 is  ERROR_NO_SYSTEM_RESOURCES

Testing updated vdservice.exe
Comment 15 Arnon Gilboa 2012-09-16 11:00:51 UTC 
Created attachment 613394 [details]
vdservice: retry virtio-serial read on ERROR_NO_SYSTEM_RESOURCES (1450)
Comment 16 Arnon Gilboa 2012-09-16 11:01:31 UTC 
Created attachment 613395 [details]
vdservice: stop service on virtio failure
Comment 17 Marian Krcmarik 2012-10-02 18:24:58 UTC 
Grant,

We are not able to reproduce this bug for verification purposes, Could I kindly ask you for helping with verification? Would you be willing verify official build which I will provide to you before release?

Thank you in advance for response.

Marian Krcmarik
Comment 18 Grant Williamson 2012-10-03 09:56:14 UTC 
I am running the 0.1-12 testing now.
Comment 23 errata-xmlrpc 2012-12-04 18:17:12 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-1502.html
Note You need to log in before you can comment on or make changes to this bug.