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.
DescriptionVitaly Kuznetsov
2021-06-15 09:45:50 UTC
Hyper-V DRM driver made it to drm/next:
24994b91ecc5 MAINTAINERS: Add maintainer for hyperv video device
25bfa956561f drm/hyperv: Handle feature change message from device
76c56a5affeb drm/hyperv: Add DRM driver for hyperv synthetic video device
Consider enabling this driver for RHEL-9.0.
Note: DRM_HYPERV is mutually exclusive with legacy CONFIG_FB_HYPERV, we should either add 'hyperv_fb' to blocklist or disable it completely.
Rick - assigning directly to you to (rather than Vitaly)...
This is a case of a bug w/ Triaged keyword being automatically set due to ITR being set and I wouldn't want to see it "lost" on virt-maint's "backlog" queue.
hi Vitaly,
we checked and found it has been included in the upstream build, but still not been enabled, could you help give an earlier build for check? thanks
kernel-5.14.0-0.rc1.20210714git40226a3d96ef.18.eln112.x86_64.rpm
kernel-core-5.14.0-0.rc1.20210714git40226a3d96ef.18.eln112.x86_64.rpm
kernel-modules-5.14.0-0.rc1.20210714git40226a3d96ef.18.eln112.x86_64.rpm
[rhel@vm-197-177 boot]$ cat config-5.14.0-0.rc1.20210714git40226a3d96ef.18.eln112.x86_64 | grep -i DRM_HYPER
# CONFIG_DRM_HYPERV is not set
[rhel@vm-197-177 boot]$ cat config-5.14.0-0.rc1.20210714git40226a3d96ef.18.eln112.x86_64 | grep -i config_fb_HY
CONFIG_FB_HYPERV=m
[rhel@vm-197-177 boot]$ lsmod | grep -i hyper
hid_hyperv 20480 0
hyperv_keyboard 20480 0
hyperv_fb 53248 2
hv_vmbus 344064 7 hv_balloon,hv_utils,hv_netvsc,hid_hyperv,hv_storvsc,hyperv_keyboard,hyperv_fb
[rhel@vm-197-177 boot]$ lsmod | grep -i hyperv_fb
hyperv_fb 53248 2
hv_vmbus 344064 7 hv_balloon,hv_utils,hv_netvsc,hid_hyperv,hv_storvsc,hyperv_keyboard,hyperv_fb
[rhel@vm-197-177 boot]$
Apparently, the change is not yet in kernel-5.14.0-0.rc1.20210714git40226a3d96ef.18.eln112, the merge request just got merged
yesterday (20210715). I'd expect next build to come with CONFIG_DRM_HYPERV.
Checked on RHEL-9.0.0-20210828.2-x86_64 (5.14.0-0.rc7.54.el9.x86_64)
Now the hyperv_drm module was loaded and enabled
[root@bootp-73-199-12 rhel]# lsmod | grep hyperv_drm
hyperv_drm 24576 1
drm_kms_helper 303104 3 hyperv_drm
drm 638976 4 drm_kms_helper,hyperv_drm
hv_vmbus 143360 7 hv_balloon,hv_utils,hv_netvsc,hid_hyperv,hv_storvsc,hyperv_keyboard,hyperv_drm
[rhel@bootp-73-199-12 ~]$ lsmod | grep hyperv_fb
[rhel@bootp-73-199-12 ~]$
For gen1, it blocked by bug: https://bugzilla.redhat.com/show_bug.cgi?id=1988922
and check the basic function works on gen2 (filed a bug may related to it: https://bugzilla.redhat.com/show_bug.cgi?id=1999697)
For detail test will check as: https://docs.google.com/document/d/1y6UuoC8-QPZ89s78hCkiYvkAlwF1sYEayGQ3pC17eX8/edit#
Mark this bug as verified, and will file new bug if encounter issue during testing.
Thanks.
Comment 15Vitaly Kuznetsov
2022-04-04 07:57:11 UTC
(In reply to xxiong from comment #14)
>
> Could you help check we need add this new feature/change into RHEL9.0
> release note?
I'm not exactly sure this deserves a release note but we can certainly state something like
"DRM driver replaces legacy framebuffer driver for Hyper-V synthetic video device"