compared the two builds packages:

http://download.eng.pek2.redhat.com/rhel-9/nightly/RHEL-9-Beta/RHEL-9.0.0-20210720.1/compose/AppStream/x86_64/os/Packages/
http://download.eng.pek2.redhat.com/rhel-9/nightly/RHEL-9-Beta/RHEL-9.0.0-20210721.3/compose/AppStream/x86_64/os/Packages/

found the kernel version is different:

kernel-devel-5.13.0-1.el9.x86_64.rpm 
kernel-devel-5.14.0-0.rc2.23.el9.x86_64.rpm


and in the X.log of attachment, can found the DRM mode added which may merged by another bug: https://bugzilla.redhat.com/show_bug.cgi?id=1972122


[    83.672] (II) xfree86: Adding drm device (/dev/dri/card0)



and also see below logs in the X.log file:


[    83.864] (II) LoadModule: "modesetting"
[    83.864] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[    83.885] (II) Module modesetting: vendor="X.Org Foundation"
[    83.885] 	compiled for 1.20.11, module version = 1.20.11
[    83.885] 	Module class: X.Org Video Driver
[    83.885] 	ABI class: X.Org Video Driver, version 24.1
[    83.885] (II) LoadModule: "fbdev"
[    83.885] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[    83.885] (II) Module fbdev: vendor="X.Org Foundation"
[    83.885] 	compiled for 1.20.10, module version = 0.5.0
[    83.885] 	Module class: X.Org Video Driver
[    83.885] 	ABI class: X.Org Video Driver, version 24.1
[    83.885] (II) LoadModule: "vesa"
[    83.885] (WW) Warning, couldn't open module vesa
[    83.885] (EE) Failed to load module "vesa" (module does not exist, 0)
[    83.885] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    83.885] (II) FBDEV: driver for framebuffer: fbdev
[    84.194] (WW) Falling back to old probe method for modesetting
[    84.497] (II) modeset(1): using default device
[    84.497] (II) Loading sub module "fbdevhw"
[    84.497] (II) LoadModule: "fbdevhw"
[    84.497] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[    84.508] (II) Module fbdevhw: vendor="X.Org Foundation"
[    84.508] 	compiled for 1.20.11, module version = 0.0.2
[    84.508] 	ABI class: X.Org Video Driver, version 24.1
[    84.508] (EE) Unable to find a valid framebuffer device
[    84.508] (WW) Falling back to old probe method for fbdev
[    84.508] (II) Loading sub module "fbdevhw"

While the issue seems to appear with 5.14 kernel, I'm not convinced it is directly
related to Hyper-V DRM switch. In particular, it seems the driver was loaded
without issues:

10:55:54,082 INFO kernel:hv_vmbus: registering driver hyperv_drm
10:55:54,084 INFO kernel:hyperv_drm 5620e0c7-8062-4dce-aeb7-520c7ef76171: [drm] Synthvid Version major 3, minor 5
10:55:54,085 INFO kernel:hyperv_drm 0000:00:08.0: vgaarb: deactivate vga console
10:55:58,737 INFO kernel:Console: switching to colour dummy device 80x25
10:55:58,737 INFO kernel:[drm] Initialized hyperv_drm 1.0.0 2020 for 5620e0c7-8062-4dce-aeb7-520c7ef76171 on minor 0
10:55:59,053 INFO kernel:Console: switching to colour frame buffer device 128x48
10:55:59,825 INFO kernel:hyperv_drm 5620e0c7-8062-4dce-aeb7-520c7ef76171: [drm] fb0: hyperv_drm frame buffer device

Also, does the issue reproduce if you install an older compose and then upgrade
kernel package (only) to 5.14? Does GUI also fail to start?

I was able to reproduce the issue outside of the installer. Turns out it's Xorg
which refuses to work with 'hyperv_drm' driver on Gen1 instances. So to reproduce
the problem one can switch to "Standard (X11 display server)" when logging in 
(click on the users and then the small gear at bottom/right).

Note: Wayland seems to be happy with the driver but the installer uses Xorg
(by default? or is this the only option atm?).

The difference between Gen1 and Gen2 is that on Gen1 there is a corresponding
PCI device:

00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA (prog-if 00 [VGA controller])
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Kernel driver in use: hyperv_drm
	Kernel modules: hyperv_drm

and on Gen2 there is no. Maybe this makes a difference to Xorg?

Do you see the same kind of failure when staring Xorg manually after installation? If so: can you run "rpm -e --nodeps xorg-x11-drv-fbdev" and then try to start Xorg again?

(In reply to Adam Jackson from comment #14)
> Do you see the same kind of failure when staring Xorg manually after
> installation?

Yes,

# X

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux dhcp-8-30-139.lab.eng.rdu2.redhat.com 5.14.0-0.rc4.35.el9.x86_64 #1 SMP Tue Aug 3 13:02:44 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-0.rc4.35.el9.x86_64 root=UUID=0712844d-faca-4bec-8123-e5daf7b239d8 ro resume=UUID=dd32ad3b-1bd9-4ae2-8f4f-fee6b6436018 console=tty0 console=ttyS0
Build Date: 22 June 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-2.el9 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep  2 11:59:17 2021
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.


> If so: can you run "rpm -e --nodeps xorg-x11-drv-fbdev" and
> then try to start Xorg again?

Doesn't seem to change anything,

# rpm -e --nodeps xorg-x11-drv-fbdev
# X

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux dhcp-8-30-139.lab.eng.rdu2.redhat.com 5.14.0-0.rc4.35.el9.x86_64 #1 SMP Tue Aug 3 13:02:44 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-0.rc4.35.el9.x86_64 root=UUID=0712844d-faca-4bec-8123-e5daf7b239d8 ro resume=UUID=dd32ad3b-1bd9-4ae2-8f4f-fee6b6436018 console=tty0 console=ttyS0
Build Date: 22 June 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-2.el9 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep  2 12:01:24 2021
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)

Thanks Vitaly,

I checked the same result:


[rhel@bootp-73-199-228 ~]$ cat log.txt 
xauth:  file /home/rhel/.serverauth.4691 does not exist


X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux bootp-73-199-228.lab.eng.pek2.redhat.com 5.14.0-1.el9.x86_64 #1 SMP Mon Aug 30 21:21:29 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-1.el9.x86_64 root=/dev/mapper/rhel_bootp--73--199--228-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_bootp--73--199--228-swap rd.lvm.lv=rhel_bootp-73-199-228/root rd.lvm.lv=rhel_bootp-73-199-228/swap rhgb quiet
Build Date: 10 August 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-3.el9 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/rhel/.local/share/xorg/Xorg.0.log", Time: Fri Sep  3 13:37:21 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/home/rhel/.local/share/xorg/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
[rhel@bootp-73-199-228 ~]$ rpm -e --nodeps xorg-x11-drv-fbdev
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied)
[rhel@bootp-73-199-228 ~]$ sudo -s

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for rhel: 
[root@bootp-73-199-228 rhel]# rpm -e --nodeps xorg-x11-drv-fbdev
[root@bootp-73-199-228 rhel]# exit
exit
[rhel@bootp-73-199-228 ~]$ cat log2.txt 
xauth:  file /home/rhel/.serverauth.33390 does not exist


X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux bootp-73-199-228.lab.eng.pek2.redhat.com 5.14.0-1.el9.x86_64 #1 SMP Mon Aug 30 21:21:29 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-1.el9.x86_64 root=/dev/mapper/rhel_bootp--73--199--228-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_bootp--73--199--228-swap rd.lvm.lv=rhel_bootp-73-199-228/root rd.lvm.lv=rhel_bootp-73-199-228/swap rhgb quiet
Build Date: 10 August 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-3.el9 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/rhel/.local/share/xorg/Xorg.0.log", Time: Fri Sep  3 13:39:21 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/home/rhel/.local/share/xorg/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
[rhel@bootp-73-199-228 ~]$

Can you test this X server build please:

http://people.redhat.com/~jadahl/1988922/

Download these to the vm under test and install them with 'rpm -Fvh *.rpm'. This build removes the old PCI-specific device probe code, which _ought_ to be mostly unused these days but which I suspect may be causing some internal confusion during autoconfiguration.

(In reply to Adam Jackson from comment #19)
> Can you test this X server build please:
> 
> http://people.redhat.com/~jadahl/1988922/
> 

This build seems to work for me, thanks! Note: I haven't tried the
installer but I'm able to log into Xorg session. I'm attaching
Xorg.0.log in case you need it.

(In reply to Adam Jackson from comment #19)
> Can you test this X server build please:
> 
> http://people.redhat.com/~jadahl/1988922/
> 
> Download these to the vm under test and install them with 'rpm -Fvh *.rpm'.
> This build removes the old PCI-specific device probe code, which _ought_ to
> be mostly unused these days but which I suspect may be causing some internal
> confusion during autoconfiguration.

Hi Adam, this sounds like a generic bug in the upstream Xorg? 
Can you please share the changes and will you get the fix into the upstream?
It's still unclear to me why the Xorg works fine with the old "hyperv_fb" driver.

(In reply to Vitaly Kuznetsov from comment #20)
> (In reply to Adam Jackson from comment #19)
> > Can you test this X server build please:
> > 
> > http://people.redhat.com/~jadahl/1988922/
> > 
> 
> This build seems to work for me, thanks! Note: I haven't tried the
> installer but I'm able to log into Xorg session. I'm attaching
> Xorg.0.log in case you need it.

Hi Vitaly/Adam,

I also checked with these builds, and the GUI display window can launch via startx.

But I found there are some failed msg if using: startx &> first_0, as below:
-----------------------------------

xauth:  file /home/rhel/.serverauth.1369 does not exist


X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux bootp-73-199-228.lab.eng.pek2.redhat.com 5.14.0-1.el9.x86_64 #1 SMP Mon Aug 30 21:21:29 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-1.el9.x86_64 root=/dev/mapper/rhel_bootp--73--199--228-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_bootp--73--199--228-swap rd.lvm.lv=rhel_bootp-73-199-228/root rd.lvm.lv=rhel_bootp-73-199-228/swap rhgb quiet
Build Date: 02 September 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-3.el9_b.jx1 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/rhel/.local/share/xorg/Xorg.0.log", Time: Mon Sep 13 17:01:26 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open hyperv_drm: /usr/lib64/dri/hyperv_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri)
failed to load driver: hyperv_drm
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
-----------------------------------

And there will no fail msg if just run: startx （screenshot attached).

Thanks

(In reply to xxiong from comment #27)

> MESA-LOADER: failed to retrieve device information
> MESA-LOADER: failed to open hyperv_drm: /usr/lib64/dri/hyperv_drm_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib64/dri)
> failed to load driver: hyperv_drm

Adam certainly knows better but AFAIU these are not fatal, they just inform
that there's no specific dri driver for Hyper-V (because nobody wrote it yet).
We should be OK with it for installer purposes I guess.

(In reply to Dexuan Cui from comment #26)
> (In reply to Adam Jackson from comment #19)
> > Can you test this X server build please:
> > 
> > http://people.redhat.com/~jadahl/1988922/
> > 
> > Download these to the vm under test and install them with 'rpm -Fvh *.rpm'.
> > This build removes the old PCI-specific device probe code, which _ought_ to
> > be mostly unused these days but which I suspect may be causing some internal
> > confusion during autoconfiguration.
> 
> Hi Adam, this sounds like a generic bug in the upstream Xorg? 
> Can you please share the changes and will you get the fix into the upstream?
> It's still unclear to me why the Xorg works fine with the old "hyperv_fb"
> driver.

It would be great if we can understand why the old "hyperv_fb" driver works while the "hyperv_drm" can't.

(In reply to Dexuan Cui from comment #30)
> (In reply to Dexuan Cui from comment #26)
> > (In reply to Adam Jackson from comment #19)
> > > Can you test this X server build please:
> > > 
> > > http://people.redhat.com/~jadahl/1988922/
> > > 
> > > Download these to the vm under test and install them with 'rpm -Fvh *.rpm'.
> > > This build removes the old PCI-specific device probe code, which _ought_ to
> > > be mostly unused these days but which I suspect may be causing some internal
> > > confusion during autoconfiguration.
> > 
> > Hi Adam, this sounds like a generic bug in the upstream Xorg? 
> > Can you please share the changes and will you get the fix into the upstream?
> > It's still unclear to me why the Xorg works fine with the old "hyperv_fb"
> > driver.
> 
> It would be great if we can understand why the old "hyperv_fb" driver works
> while the "hyperv_drm" can't.


For hyperv_fb, xf86-video-fbdev DDX is used and for hyperv_drm it is xf86-video-modesetting. Possibly the bug only happen with the later.

To ssh://pkgs.devel.redhat.com/rpms/xorg-x11-server
   fcb1551..1df105c  rhel-9.0.0-beta -> rhel-9.0.0-beta
Found a gating.yaml file in the repo and it is properly configured
Building xorg-x11-server-1.20.11-4.el9 for rhel-9.0.0-beta-candidate
Created task: 40090287
Task info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=40090287

Thanks Vitaly/Tomas,

I checked with compose: RHEL-9.0.0-20211006.6 (xorg-x11-server-Xorg-1.20.11-4.el9_b.x86_64）:

1. the GEN1 and GEN2 GUI installation work well--PASS
2. checked GUI login with each display server option--PASS
3. check the command startx---can start GUI well, below error log display
4. check the command X---cannot start GUI, and below error log will display when client connect to the x sever----->will file another bug to trace 3,4



--------------------startx.log


[rhel@vm-198-65 ~]$ cat startx.log 
xauth:  file /home/rhel/.serverauth.49626 does not exist


X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux vm-198-65.lab.eng.pek2.redhat.com 5.14.0-1.6.1.el9.x86_64 #1 SMP Mon Oct 4 14:14:47 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-1.6.1.el9.x86_64 root=/dev/mapper/rhel_vm--198--65-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_vm--198--65-swap rd.lvm.lv=rhel_vm-198-65/root rd.lvm.lv=rhel_vm-198-65/swap rhgb quiet
Build Date: 01 October 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-4.el9_b 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/rhel/.local/share/xorg/Xorg.0.log", Time: Fri Oct  8 11:22:18 2021
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open hyperv_drm: /usr/lib64/dri/hyperv_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri)
failed to load driver: hyperv_drm
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

[rhel@vm-198-65 ~]$ 


-------------------------------X.log


[rhel@vm-198-65 ~]$ cat X.log 

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System:  4.18.0-193.28.1.el8_2.x86_64 
Current Operating System: Linux vm-198-65.lab.eng.pek2.redhat.com 5.14.0-1.6.1.el9.x86_64 #1 SMP Mon Oct 4 14:14:47 EDT 2021 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-1.6.1.el9.x86_64 root=/dev/mapper/rhel_vm--198--65-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_vm--198--65-swap rd.lvm.lv=rhel_vm-198-65/root rd.lvm.lv=rhel_vm-198-65/swap rhgb quiet
Build Date: 01 October 2021  12:00:00AM
Build ID: xorg-x11-server 1.20.11-4.el9_b 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct  8 11:23:06 2021
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open hyperv_drm: /usr/lib64/dri/hyperv_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri)
failed to load driver: hyperv_drm
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
(II) Server terminated successfully (0). Closing log file.

(In reply to xxiong from comment #44)

> MESA-LOADER: failed to open hyperv_drm: /usr/lib64/dri/hyperv_drm_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib64/dri)
> failed to load driver: hyperv_drm

AFAIU this 'error' just means that there's no 'hyperv_drm' dri driver written
yet. Given that our bright future is Wayland, it is unlikely that anyone would
actually want to implement this driver for Xorg. You will likely find the same
error even when Xorg is started from gdm/installer/...

Just my $0.02.

(In reply to Vitaly Kuznetsov from comment #45)
> (In reply to xxiong from comment #44)
> 
> > MESA-LOADER: failed to open hyperv_drm: /usr/lib64/dri/hyperv_drm_dri.so:
> > cannot open shared object file: No such file or directory (search paths
> > /usr/lib64/dri)
> > failed to load driver: hyperv_drm
> 
> AFAIU this 'error' just means that there's no 'hyperv_drm' dri driver written
> yet. Given that our bright future is Wayland, it is unlikely that anyone
> would
> actually want to implement this driver for Xorg. You will likely find the
> same
> error even when Xorg is started from gdm/installer/...
> 
> Just my $0.02.

Right I can second that, almost all user space graphics leaning towards modeseting including intel and nvidia.

Can you please share these packages to reproduce this issue :
* RHEL-9.0.0-20210729.2-x86_64-dvd1.iso
* kernel-5.14.0-0.rc3.29.el9.x86_64.rpm   
* xorg-x11-server-Xorg-1.20.11-2.el9.x86_64

(In reply to Saurabh Sengar from comment #50)
> Can you please share these packages to reproduce this issue :
> * RHEL-9.0.0-20210729.2-x86_64-dvd1.iso
> * kernel-5.14.0-0.rc3.29.el9.x86_64.rpm   
> * xorg-x11-server-Xorg-1.20.11-2.el9.x86_64

Hi Saurabh,

This issue already been fixed, do you still need the old builds?  for what?

thanks

Hi Xxiong,
We would like to reproduce the issue and fix suggested, so that we can document it for future reference.

(In reply to Saurabh Sengar from comment #52)
> Hi Xxiong,
> We would like to reproduce the issue and fix suggested, so that we can
> document it for future reference.

Hi Saurabh,

Not found the exactly same kernel, but the xorg is same (which is the issue component)

http://people.redhat.com/~yuxisun/kernel-5.14.0-0.rc2.23.el9/
http://people.redhat.com/~yuxisun/xorg-x11-server-Xorg-1.20.11-2.el9.x86_64.rpm


Thanks