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.
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.
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.