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:
The window size of remote-viewer is bigger than normal after install virtio-win-prewhql-204 version viogpudo driver. Didn't find this issue with the previous several versions of the driver.
Version-Release number of selected component (if applicable):
virtio-win-prewhql-204.iso
qemu-kvm-5.2.0-16.module+el8.4.0+11721+c8bbc1be.3.x86_64
kernel-4.18.0-305.el8.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
How reproducible:
100%
Steps to Reproduce:
1. bootup win10-32 guest with viogpudo driver.
2. connect guest via remote-viewer vnc://127.0.0.1:5900
Actual results:
the window size is bigger than normal.
Expected results:
the window size should be the default.
Additional info:
I checked the default resolution after installing viogpudo driver is 1280x1024, Is that set as default resolution since prewhql207? (208 as same)so maybe that's the root cause or not.
before build 204 the list of supported resolutions on Win10 platforms was
{640, 480},
{800, 600},
{1024, 768},
from build 204 this list was extended with the new ones
{1280, 1024},
{1920, 1080},
{2560, 1600},
Windows automatically picks up the maximum resolution that both display
and monitor can support as recommended.
Best regards,
Vadim.
(In reply to Vadim Rozenfeld from comment #3)
> Hi Dehan,
> What would be the expected behaviour then?
> Keeping 1024x768 as the default resolution?
>
> Best,
> Vadim
Actually, there are two default resolutions for win10+/win8.1+, some of them keep 1024x768, but some are not the same as I remembered. so that'll be great to keep one resolution for all windows versions. so yes, I think it's proper that choose 1024x768 as the default resolution.
Comment 7RHEL Program Management
2023-05-01 07:28:14 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 9RHEL Program Management
2023-08-15 11:24:57 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.