Bug 728259

Summary:	Windows 7 x64 updates driver to 32bit version
Product:	Red Hat Enterprise Linux 8	Reporter:	David Jaša <djasa>
Component:	spice-qxl-xddm	Assignee:	David Blechter <dblechte>
Status:	CLOSED WONTFIX	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	---	CC:	bsettle, dblechte, knoel, mkenneth, mkrcmari, pvine, rbalakri, sstutsma, uril, yeylon, ykamay, yvugenfi
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Windows
Whiteboard:
Fixed In Version:	qxl-win-unsigned-0.1-20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-26 17:13:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Jaša 2011-08-04 14:17:37 UTC

Description of problem:
SSIA

Version-Release number of selected component (if applicable):
virtio-win-1.0.2-0.52454.el5
Windows 7 x64

How reproducible:
always

Steps to Reproduce:
1. Go to Device manager, unfold Display adapters
2. right-click Update Driver Software...
3. hit "Browse my computer for driver software"
4. enter "a:\" to "Search for driver in this location" input
  
Actual results:
Windows returns "Windows found driver software for your device but encountered an error while attempting to install it. Driver is not intended for this platform". Windows however *does install x32 driver* that makes display unusable after reboot (in fallback 640x480/8b mode)

Expected results:
Windows installs x64 driver like it does when pointed to "a:\amd64"

Additional info:

Comment 1 Ronen Hod 2011-08-04 15:49:29 UTC

Surprisingly, there is no intelligent automatic selection! The user/software have to provide a full path in order to reliably use the proper driver.

For more info read
https://bugzilla.redhat.com/show_bug.cgi?id=708930#c9

Closing although not in my domain.

Comment 4 Ronen Hod 2011-08-06 13:57:01 UTC

Thanks Yaniv, I got it wrong.

Comment 5 Marian Krcmarik 2012-01-04 16:22:16 UTC

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

Comment 6 Marian Krcmarik 2012-01-04 16:25:23 UTC

qspice is not right component for this bug and causes that this bug will be forgotten.

As far as I understand It should go to QXL component and be resolved according to comment #2 and comment #3

Comment 7 David Blechter 2014-02-11 23:23:20 UTC

there are no plans for whql for 3.4, moving to future releases

Comment 11 Sandy Stutsman 2015-08-26 17:13:24 UTC

Confirmed that the win-qxl 64 bit drivers will install qxl-win-0.1-21 build.