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 1758524 - Windows 10 guest with QXL WDDM driver screen resolution issue
Summary: Windows 10 guest with QXL WDDM driver screen resolution issue
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-qxl-wddm-dod
Version: 8.2
Hardware: x86_64
OS: Windows
high
high
Target Milestone: rc
: 8.3
Assignee: ybendito
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-04 12:38 UTC by Giuseppe
Modified: 2020-11-04 03:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 03:44:38 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Trial qxl-wddm-dod driver (1) (675.04 KB, application/zip)
2019-10-15 09:17 UTC, ybendito
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4768 0 None None None 2020-11-04 03:44:43 UTC

Description Giuseppe 2019-10-04 12:38:15 UTC
Description of problem:
I have installed a Windows 10 VM using a 7" display with a 800x480 screen resolution. The qxl driver used is the: qxl-wddm-dod-0.19 but the minimum resolution available on Windows 10 display settings is 800x600.

There is already a similar Bug ID: 1477492, but this issue could be present again with another small display with a different resolution.


Version-Release number of selected component:
qxl-wddm-dod-0.19

How reproducible: always


Steps to Reproduce:
1. install a Window 10 VM on a machine with a small monitor
2. Go to Windows display settings
3. Try to set a correct resolution but only the 800x600 resolution is available

Actual results:
Invalid screen resolution

Expected results:
Correct 800x480 screen resolution available on the list of supported resolution

Additional info:
I have changed locally the code and I have a working version signed with a developer certificate. Is there any side effect to set a MIN_WIDTH_SIZE to 320 and MIN_HEIGHT_SIZE to 200 instead of 800 and 600?

Comment 2 ybendito 2019-10-15 09:17:01 UTC
Created attachment 1625886 [details]
Trial qxl-wddm-dod driver (1)

Comment 3 ybendito 2019-10-15 09:38:29 UTC
In general, Win10 requirements include display of 800x600
https://www.microsoft.com/en-us/windows/windows-10-specifications#primaryR2
Attached driver that includes lower resolutions (800*480 and also lower up to 320*200, if available).
Please respond whether it works as expected.

Comment 5 Daniel Schaefer 2019-10-21 13:47:03 UTC
I just spoke to the KAL engineers. They were able to verify the code on their simulated environments on a laptop, but did not yet have access again to the real ATM hardware. Access to the hardware is unfortunately a bit of a bottleneck here as the machine is currently running different tests by the bank. As soon as this is finished, Giuseppe will verify the code on the real ATM and update the BZ.

Thanks for the super-fast turn-around!

Comment 6 Giuseppe 2019-10-22 16:25:13 UTC
Hi,
I have tested the driver on the machine and it works properly.

Thanks,
Giuseppe

Comment 7 David Blechter 2019-12-17 15:27:56 UTC
The plan is to release the new version of the driver in rhel 8.3

Comment 8 Giuseppe 2020-01-16 07:34:15 UTC
Hi,
Testing the drivers on some machines having the monitor in portrait position, the windows screen is shown flipped. Is it possible to add the "portrait (flipped)" and also the "landscape (flipped)" configurations to the QXL as for standard windows driver?

Best Regards,
Giuseppe

Comment 9 David Blechter 2020-01-16 12:43:57 UTC
(In reply to Giuseppe from comment #8)
> Hi,
> Testing the drivers on some machines having the monitor in portrait
> position, the windows screen is shown flipped. Is it possible to add the
> "portrait (flipped)" and also the "landscape (flipped)" configurations to
> the QXL as for standard windows driver?
> 
> Best Regards,
> Giuseppe

Hi,
Please, open a new BZ for this new requirement.

thanks David

Comment 10 ybendito 2020-05-29 15:33:55 UTC
The resolution is fixed in spice-qxl-wddm-dod-0.20-0
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1126115

Comment 17 errata-xmlrpc 2020-11-04 03:44:38 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 (spice-qxl-wddm-dod bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4768


Note You need to log in before you can comment on or make changes to this bug.