Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 683166

Summary:	vdagent: should not fail to start when no qxl driver installed
Product:	Red Hat Enterprise Linux 8	Reporter:	Barak <bazulay>
Component:	spice-vdagent-win	Assignee:	Arnon Gilboa <agilboa>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	acathrow, alevy, bsanford, cmeadors, dblechte, iheim, jrb, kgrainge, mkrcmari, Rhev-m-bugs, uril, ykaul
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Previously, you could not start the SPICE agent on Windows Server guests if the QXL driver was not installed. This dependency has been removed and you can now use the SPICE agent on Windows Server guests without the QXL driver.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-15 15:36:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	683162

Description Barak 2011-03-08 17:58:49 UTC

Seperation of the vdagent from spice is required to obtain local mouse when connecting to win server VM.

SInce current vdagent depends on qxl to exist, it fails starting on win server platforms:
  w2k3 32/64/r2
  w2k8 23/64/r2

The logic that fails vdagent start should be removed and allow it to come up even when no qxl driver is available.

Comment 2 Alon Levy 2011-03-20 12:19:25 UTC

*** Bug 616795 has been marked as a duplicate of this bug. ***

Comment 3 Marian Krcmarik 2011-07-25 19:03:01 UTC

Verified on vdagent-win-0.1-7 with Standard VGA Graphics adapter.

Comment 4 Kate Grainger 2011-12-12 01:18:29 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, you could not start the SPICE agent on Windows Server guests if the QXL driver was not installed. This dependency has been removed and you can now use the SPICE agent on Windows Server guests without the QXL driver.

Comment 5 errata-xmlrpc 2011-12-15 15:36:35 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