Bug 727886 - qxl-win: regression: revision 2 not supported because of too strict io range check
Summary: qxl-win: regression: revision 2 not supported because of too strict io range ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-qxl-xddm
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Alon Levy
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-03 14:21 UTC by Alon Levy
Modified: 2019-10-10 13:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-15 12:20:49 UTC
Type: ---
Target Upstream Version:

Attachments (Terms of Use)
fix (1.17 KB, patch)
2011-08-03 14:21 UTC, Alon Levy 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Alon Levy 2011-08-03 14:21:17 UTC 
Created attachment 516526 [details]
fix

Description of problem:
driver qxl-win-0.1-8 fails to load on a vm running qxl revision 2 with an io bar of revision 2, i.e. [0..QXL_IO_DESTROY_ALL_SURFACES]

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.160.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. start qemu-kvm of the above version with a qxl device (-vga qxl) with a windows vm (xp 32, win7 32 tested by me, others reported to fail the same way: win7 64)
2. try installing the brew built qxl-win-0.1-8 driver (https://brewweb.devel.redhat.com/buildinfo?buildID=174558)
  
Actual results:
Installation fails with Code 10.
Looking in c:\windows\setupapi.log you will see:
#I163 Device not started: Device has problemn: 0x0a: CM_PROB_FAILED_START.
Device manager will show a yellow exclamation mark next to the device name "Red Hat QXL GPU" under "Display Adapter"

Expected results:
Installation successful.

Additional info:
Comment 1 Alon Levy 2011-08-03 14:22:36 UTC 
Note: for beta 1 this is irrelevant, since we are using 2.2 driver. For beta 2, assuming we get the driver to be acceptable otherwise, this is a must.
Note You need to log in before you can comment on or make changes to this bug.