Bug 749836

Summary: QXL driver isn't able to start on 32b windows with /3GB switch
Product: Red Hat Enterprise Linux 8 Reporter: David Jaša <djasa>
Component: spice-qxl-xddmAssignee: Alon Levy <alevy>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: acathrow, dblechte
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-31 13:22:18 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-10-28 16:59:04 UTC
Description of problem:
SSIA. 

Version-Release number of selected component (if applicable):
5.1.0.10010 (8/28/2011)

How reproducible:
always

Steps to Reproduce:
1. install driver in fresh Windows XP guest, reboot and verify it's working
2. go to System Properties -> Advanced -> Startup and Recovery Options -> Edit
3. add /3GB switch to the last line
4. reboot
  
Actual results:
vga driver is used, when trying to switch to qxl manually, error about not being to able to start the driver up pops up

Expected results:
qxl driver works

Additional info:
Prevents allowing memory-intensive apps in guest more than 2 GB of RAM when using QXL driver.

Comment 1 Alon Levy 2011-10-31 12:58:37 UTC
Hi,

 I'm not sure we want to fix this in the XDDM (current) driver. Is this a must have? if it is possible to postpone, I would rather we first have a WDDM driver, and solve it there.

Alon
p.s. we don't yet have a timeline for a WDDM driver. But we are working on one.

Comment 2 Andrew Cathrow 2011-10-31 13:22:18 UTC
XP is already out of mainstream support and in extended support period and this is a niche use case so we can skip this.

Comment 3 David Jaša 2011-11-01 15:57:23 UTC
Interestingly enough, Windows 7 32b don't have this issue, so it it really limited to XP.