What were you trying to do that didn't work?

When we try to boot an RHEL 9.2 VM (the VM SKU is “Standard M896ixds 32 v3 (896 vcpus, 30400 GiB memory)”) on Azure, the VM enters emergency mode because the Hyper-V storage device driver (hv_storvsc) fails to load automatically.

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

[?2004hdracut:/# journalctl -u systemd-udevd | cat
[?2004l
Mar 02 00:08:11 lisa--601-e0-n0 systemd[1]: Starting Rule-based Manager for Device Events and Files...
Mar 02 00:08:11 lisa--601-e0-n0 systemd-udevd[7578]: Using default interface naming scheme 'rhel-9.0'.
Mar 02 00:08:11 lisa--601-e0-n0 systemd[1]: Started Rule-based Manager for Device Events and Files.
Mar 02 00:08:14 lisa--601-e0-n0 systemd-udevd[7578]: libkmod: conf_files_list: opendir(/etc/modprobe.d): Too many open files
Mar 02 00:08:14 lisa--601-e0-n0 systemd-udevd[7578]: libkmod: conf_files_list: opendir(/lib/modprobe.d): Too many open files
Mar 02 00:08:14 lisa--601-e0-n0 systemd-udevd[7578]: Failed to send readiness notification, ignoring: Too many open files

Please provide the package NVR for which bug is seen:

 systemd 252-14.el9_2.5 

How reproducible:

100%

Steps to reproduce

Create an RHEL 9.2 VM (the VM SKU is “Standard M896ixds 32 v3 (896 vcpus, 30400 GiB memory)”) on Azure, the VM enters emergency mode.

Expected results

The VM should boot up normally.

Actual results

The VM enters emergency mode.