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.
There's some more data that could help identify the problem: under QXL KMDOD properties / Details, I have:
- Status = DN_HAS_PROBLEM | DN_DISABLEABLE | DN_NT_ENUMERATOR | DN_NT_DRVIER
- Problem Code = 0x2B
- Problem Status = 0x0
I think I have at least one good reason why the most recent (0.3) driver won't work on a basic OVMF build. The source contains calls to x86BiosCall() on the driver/device initialization path.
OVMF (and UEFI firmware in general) doesn't need to provide a VGA BIOS. It can, optionally, with a CSM (Compatibility Support Module), but it's not required.
Version 0.2 of qxlwddm was apparently not tied to a VGA BIOS. Is the new dependency in 0.3 unavoidable? Thank you.
(In reply to Laszlo Ersek from comment #6)
> I think I have at least one good reason why the most recent (0.3) driver
> won't work on a basic OVMF build. The source contains calls to x86BiosCall()
> on the driver/device initialization path.
>
> OVMF (and UEFI firmware in general) doesn't need to provide a VGA BIOS. It
> can, optionally, with a CSM (Compatibility Support Module), but it's not
> required.
>
> Version 0.2 of qxlwddm was apparently not tied to a VGA BIOS. Is the new
> dependency in 0.3 unavoidable? Thank you.
Unfortunately yes, in VGA mode I don't have any other options to restore the resolution
after returning from S3 either then calling Int10 or any appropriated ACPI method.
This problem will be fixed after adding support for QXL mode.
(In reply to Vadim Rozenfeld from comment #8)
> Changing the status. The driver is available at
> https://brewweb.devel.redhat.com/buildinfo?buildID=323507
>
> It is not required to specify qxl-vga.revision=3 anymore.
>
> Thanks,
> Vadim.
Hi Vadim,
I still hit the same issue on win8-32 guest could you please double check ?
Thanks
Min
(In reply to dengmin from comment #10)
> (In reply to Vadim Rozenfeld from comment #8)
> > Changing the status. The driver is available at
> > https://brewweb.devel.redhat.com/buildinfo?buildID=323507
> >
> > It is not required to specify qxl-vga.revision=3 anymore.
> >
> > Thanks,
> > Vadim.
>
> Hi Vadim,
> I still hit the same issue on win8-32 guest could you please double check
> ?
Hi Min,
Do you mean that that you cannot enter S3 on win8-32 guest even with qxl driver installed?
Thanks,
Vadim.
> Thanks
> Min