MantisBT - Issues

0000606: Anaconda rejects x86_64_v2 ISO on x86_64-v3 systems - "Error setting up repositories"

Sat, 21 Feb 2026 22:45:51 +0000

When booting the AlmaLinux 10.1 x86_64_v2 DVD ISO on an x86_64 system, anaconda fails to set up the installation source with "Error setting up repositories".

Root cause: The .discinfo file on the ISO contains "x86_64_v2" as the architecture, but anaconda's is_valid_install_disk() function in pyanaconda/modules/payloads/source/utils.py performs a strict equality check against blivet.arch.get_arch() which returns "x86_64". The check fails, causing anaconda to reject the valid installation media.

The same issue affects _find_first_iso_image() in the same file.

x86_64_v2 is a microarchitecture level of x86_64, not a different architecture. Systems running x86_64_v2 code still report as x86_64 via uname.

0000607: [AlmaLinux][Mana_IB][RDMA][Backport] RDMA/mana_ib: Take CQ type from the device type P1

Mon, 02 Feb 2026 07:31:08 +0000

Hi,

Request backport of the following task. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/drivers/infiniband/hw/mana?id=f972bde7326e9cd3498c137a052f2034f975ebae

0000605: [AlmaLinux]{hv_netvsc][Backport] net: hv_netvsc: reject RSS hash key programming without RX indirection table

Thu, 29 Jan 2026 13:41:08 +0000

Request backport of the following patch..

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=d23564955811

0000604: [AlmaLinux][Mana][Backport] net: mana: Implement ndo_tx_timeout and serialize queue resets per port.

Thu, 29 Jan 2026 13:07:17 +0000

Hi,

Request backport of the following patch to all active kernel versions. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3b194343c250

0000603: [AlmaLinux][MANA][Backport] [GB200] Backport patch for handling device slow probe on GB200

Thu, 29 Jan 2026 11:53:41 +0000

Request backport of the following patch.

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=9bf66036d686b9a67000ba22bd94be13a4ea79ac

0000602: [AlmaLinux][storvsc][Backport] Backport storvsc patch for handling MODE_SENSE_10

Tue, 27 Jan 2026 06:29:49 +0000

Hi,
Customer Reported issue. Need backport of the patch on priority for active alma versions. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?h=v6.19-rc7&id=9eacec5d18f98f89be520eeeef4b377acee3e4b8

This is a critical fix to storvsc. It fixes VM hung on starting up when the VM is initializing a disk and host may return unsupported results for MODE_SENSE_10.

0000594: Alma 10.1 rdp install broken

Wed, 21 Jan 2026 04:14:05 +0000

I tried to install alma 10.1 via pxe or boot.iso under legacy bios and uefi. I tried under kvm-vm and dell physical server.
boot.iso md5sum is "11d14e7e80f243e1e10d99a6c5bda92b"

rdp install parameter like “inst.rdp inst.rdp.username=userxxx inst.rdp.password=passxxx” failed.

rdp installation is important for EL10, because many Dell/HP/Lenovo server BMC with matrox g200 has no wayland support. so gui installation is not possible without rdp.

RHEL 10.1 rdp installation works fine.

tail /tmp/syslog I got the error message below:

ERR gnome-remote-desktop:[14:02:01:259] [3286:00000e4f] [WARN][com.freerdp.core.peer] - [peer_unexpected_client_message]: Unexpected client message in state CONNECTION_STATE_FINALIZATION_FONT_LIST, missing flag FINALIZE_CS_FONT_LIST_PDU [0x00000100]
14:02:01,301 NOTICE gnome-remote-de:[RDP.CLIPRDR] Client capabilities: long format names, stream file clip, file clip no file paths, can lock clip data, huge file support
14:02:01,308 WARNING gnome-remote-de:Failed to start screen cast stream: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to start stream: Couldn't connect pipewire context
14:02:01,308 ERR gnome-remote-desktop:[14:02:01:294] [3286:00000cd6] [ERROR][com.freerdp.core.peer] - [rdp_set_error_info]: ERRINFO_RPC_INITIATED_DISCONNECT [0x00010001]

0000601: [AlmaLinux][hv_netvsc][Distros][Backport][GB200] hv_netvsc module reload fails for ARM64 SKUs

Fri, 16 Jan 2026 15:59:54 +0000

Request backport of the following patches for all current kernel versions.

bee35b7161aa RDMA/mana_ib: Handle net event for pointing to the current netdev
a8445cfec101 net: mana: Change the function signature of mana_get_primary_netdev_rcu

0000600: Set minor version in `kickstart` repo's `.treeinfo`

Fri, 16 Jan 2026 14:25:26 +0000

With the kickstart tree's content frozen on release, it would be helpful if the `.treeinfo` included the minor release in the version.

This would permit content republication tools (like katello/RedHat Satellite) to correctly identify installation trees for matching install media.

Folks doing less advanced caching would also benefit from the file containing a clear identification of the tree.

No change to the `os` .treeinfo should be made. That should still have no minor verision information.

I'd love to see this in both 9 and 10.

0000591: Golang is compiled for v3 instructions support / Almalinux 10 x86-64-v2

Fri, 09 Jan 2026 06:32:16 +0000

Golang package build on Almalinux 10 x86-64-v2 release is not able to execute:
"This program can only be run on AMD64 processors with v3 microarchitecture support."

Also reported here by a user: https://forums.almalinux.org/t/golang-x86-64-v2-requires-v3/6841

0000599: [nvidia] Have dashvariant also provide non-dash names.

Tue, 06 Jan 2026 18:38:04 +0000

The 64k stack kernel for aarch64 appears to be missing a provides on the non-dashvariant name. This blocks install of cuda.

0000598: rpm missing in initrd 10.1

Tue, 06 Jan 2026 08:38:02 +0000

When starting an anaconda kickstart install no "rpm" command is in iniitrd :

- rpm is missing

Why is this of high importance (for me):

I use rpm / dnf to install packages before kickstart runs.
For example:

- support better luks passwords / python3-xkcdpass and clevis-luks,

0000597: nvidia package or procedure need to tweak

Thu, 18 Dec 2025 07:24:38 +0000

Hi:
according to AlmaLinux nvidia document: https://wiki.almalinux.org/documentation/nvidia.html
you only need two lines to use nvidia card:
dnf install almalinux-release-nvidia-driver
dnf install dnf install almalinux-release-nvidia-driver nvidia-driver-cuda

reboot and now we can use "nvidia-smi" to check the card status.

I install a brand new AlmaLinux 10.1 with a telsa T4, after procedure above, the "nvidia-smi" is very slow, the card is stay at P0 27W state even the system is idle. and system show error message at boot:
[ 6.698324] NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563
[ 6.698361] NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563
[ 6.698416] NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563
[ 6.698434] NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563

the fix it is easy. just "dracut -v -f" and reboot then everything will be fine. but it took me whole day to find the reason.
below is the diff of "bad" and "good" initrdramfs:

diff -ru /tmp/bad /tmp/good
--- /tmp/bad 2025-12-18 15:03:03.105406573 +0800
+++ /tmp/good 2025-12-18 15:03:09.459326822 +0800
@@ -1,8 +1,8 @@
-Image: initramfs-6.12.0-124.20.1.el10_1.x86_64.img.bad: 40M
+Image: /boot/initramfs-6.12.0-124.20.1.el10_1.x86_64.img: 29M
========================================================================
Version: dracut-107-3.el10

-Arguments: -f
+Arguments: -v -f

dracut modules:
bash
@@ -77,6 +77,7 @@
-rw-r--r-- 1 root root 2476 Jun 5 2025 etc/lvm/lvmlocal.conf
-r--r--r-- 1 root root 33 Aug 18 08:00 etc/machine-id
drwxr-xr-x 2 root root 0 Aug 18 08:00 etc/modprobe.d
+-rw-r--r-- 1 root root 193 Aug 18 08:00 etc/modprobe.d/nvidia-modeset.conf
-rw-r--r-- 1 root root 674 Aug 18 08:00 etc/modprobe.d/tuned.conf
lrwxrwxrwx 1 root root 17 Aug 18 08:00 etc/mtab -> /proc/self/mounts
lrwxrwxrwx 1 root root 24 Aug 18 08:00 etc/nsswitch.conf -> authselect/nsswitch.conf
@@ -299,12 +300,12 @@
-rwxr-xr-x 1 root root 2579664 Aug 17 08:00 usr/lib64/systemd/libsystemd-core-257-13.el10.alma.1.so
-rwxr-xr-x 1 root root 4872928 Aug 17 08:00 usr/lib64/systemd/libsystemd-shared-257-13.el10.alma.1.so
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/dracut
--rw-r--r-- 1 root root 4 Aug 18 08:00 usr/lib/dracut/build-parameter.txt
+-rw-r--r-- 1 root root 7 Aug 18 08:00 usr/lib/dracut/build-parameter.txt
-rwxr-xr-x 1 root root 8181 May 1 2025 usr/lib/dracut-crypt-lib.sh
-rwxr-xr-x 1 root root 4082 May 1 2025 usr/lib/dracut-dev-lib.sh
-rw-r--r-- 1 root root 18 Aug 18 08:00 usr/lib/dracut/dracut-107-3.el10
lrwxrwxrwx 1 root root 29 Aug 18 08:00 usr/lib/dracut/hooks -> ../../../var/lib/dracut/hooks
--rw-r--r-- 1 root root 199 Aug 18 08:00 usr/lib/dracut/hostonly-files
+-rw-r--r-- 1 root root 235 Aug 18 08:00 usr/lib/dracut/hostonly-files
-rwxr-xr-x 1 root root 27151 May 1 2025 usr/lib/dracut-lib.sh
-rw-r--r-- 1 root root 447 Aug 18 08:00 usr/lib/dracut/modules.txt
-rw-r--r-- 1 root root 0 Aug 18 08:00 usr/lib/dracut/need-initqueue
@@ -1370,6 +1371,7 @@
-rw-r--r-- 1 root root 1811 Jan 10 2025 usr/lib/kbd/unimaps/viscii.uni
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modprobe.d
-rw-r--r-- 1 root root 884 Aug 18 08:00 usr/lib/modprobe.d/dist-blacklist.conf
+-rw-r--r-- 1 root root 1039 Aug 18 08:00 usr/lib/modprobe.d/nvidia.conf
-rw-r--r-- 1 root root 821 Dec 11 2024 usr/lib/modprobe.d/systemd.conf
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64
@@ -1450,11 +1452,6 @@
-rw-r--r-- 1 root root 19492 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/char/virtio_console.ko.xz
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/crypto
-rw-r--r-- 1 root root 5976 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/crypto/padlock-aes.ko.xz
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/gpu
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/gpu/drm
--rw-r--r-- 1 root root 7456 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/gpu/drm/drm_ttm_helper.ko.xz
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/gpu/drm/ttm
--rw-r--r-- 1 root root 45756 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/gpu/drm/ttm/ttm.ko.xz
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/hid
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/hid/amd-sfh-hid
-rw-r--r-- 1 root root 21948 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/drivers/hid/amd-sfh-hid/amd_sfh.ko.xz
@@ -1720,30 +1717,19 @@
-rw-r--r-- 1 root root 24096 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/sound/core/snd-rawmidi.ko.xz
-rw-r--r-- 1 root root 6116 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/sound/core/snd-seq-device.ko.xz
-rw-r--r-- 1 root root 6304 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/kernel/sound/soundcore.ko.xz
--rw-r--r-- 1 root root 75244 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.alias
--rw-r--r-- 1 root root 69322 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.alias.bin
+-rw-r--r-- 1 root root 74736 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.alias
+-rw-r--r-- 1 root root 68971 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.alias.bin
-rw-r--r-- 1 root root 9732 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.builtin
-rw-r--r-- 1 root root 12284 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.builtin.alias.bin
-rw-r--r-- 1 root root 12061 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.builtin.bin
-rw-r--r-- 1 root root 86748 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.builtin.modinfo
--rw-r--r-- 1 root root 17349 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.dep
--rw-r--r-- 1 root root 28393 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.dep.bin
+-rw-r--r-- 1 root root 16775 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.dep
+-rw-r--r-- 1 root root 27625 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.dep.bin
-rw-r--r-- 1 root root 166 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.devname
-rw-r--r-- 1 root root 98408 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.order
--rw-r--r-- 1 root root 123 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.softdep
--rw-r--r-- 1 root root 53956 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.symbols
--rw-r--r-- 1 root root 64518 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.symbols.bin
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/weak-updates
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/weak-updates/nvidia-open
-lrwxrwxrwx 1 root root 69 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/weak-updates/nvidia-open/nvidia-drm.ko -> ../../../6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open/nvidia-drm.ko
-lrwxrwxrwx 1 root root 65 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/weak-updates/nvidia-open/nvidia.ko -> ../../../6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open/nvidia.ko
-lrwxrwxrwx 1 root root 73 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/weak-updates/nvidia-open/nvidia-modeset.ko -> ../../../6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open/nvidia-modeset.ko
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.8.1.el10_1.x86_64
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.8.1.el10_1.x86_64/extra
-drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/modules/6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open
--rw-r--r-- 1 root root 323854 Aug 18 08:00 usr/lib/modules/6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open/nvidia-drm.ko
--rw-r--r-- 1 root root 25114470 Aug 18 08:00 usr/lib/modules/6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open/nvidia.ko
--rw-r--r-- 1 root root 4578070 Aug 18 08:00 usr/lib/modules/6.12.0-124.8.1.el10_1.x86_64/extra/nvidia-open/nvidia-modeset.ko
+-rw-r--r-- 1 root root 76 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.softdep
+-rw-r--r-- 1 root root 45551 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.symbols
+-rw-r--r-- 1 root root 55061 Aug 18 08:00 usr/lib/modules/6.12.0-124.20.1.el10_1.x86_64/modules.symbols.bin
lrwxrwxrwx 1 root root 14 Aug 18 08:00 usr/lib/os-release -> initrd-release
drwxr-xr-x 2 root root 0 Aug 18 08:00 usr/lib/sysctl.d
-rw-r--r-- 1 root root 1810 Apr 30 2025 usr/lib/sysctl.d/10-default-yama-scope.conf

0000596: Clarification on NFSv4 delegation test failures (nfstest / LTP) on AlmaLinux 9.6

Thu, 18 Dec 2025 06:20:31 +0000

Hello Community,

We are validating NFS functionality on AlmaLinux 9.6 and observed failures in NFSv4 delegation tests (READ/WRITE delegation).

Functional NFS operations (open, read, write, lock) work correctly, however delegation-related checks report failures such as:

“READ delegation should be granted”

“WRITE delegation should be granted”

On the server side, we observe that no delegations are being issued:

cat /proc/net/rpc/nfsd | grep deleg
wdeleg_getattr 0

NFSv4 is enabled (+4 +4.1 +4.2), and nfsd is running normally. From our understanding, NFSv4 delegations are an optional performance optimization, and servers are allowed to not grant delegations, especially under locking or concurrent access scenarios.

Could you please confirm:

That it is expected and RFC-compliant for an NFSv4 server on AlmaLinux 9.x to not grant delegations

That delegation test failures in this case do not indicate a functional or kernel defect

Whether excluding delegation-specific tests is the correct approach for such environments

Thank you for your guidance.

Best regards,
Harish

0000595: [AlmaLinux][MANA][Backport][Distros] porting patch: net: mana: Fix incorrect speed reported by debugfs

Wed, 17 Dec 2025 13:34:53 +0000

Request backport of the following patch to all active kernel versions. Thanks.

https://lore.kernel.org/lkml/1762369468-32570-1-git-send-email-ernis@linux.microsoft.com/

0000593: perl-DBD-MySQL prevents package updates when MariaDB is in use

Fri, 12 Dec 2025 20:04:35 +0000

Newer versions of perl-DBD-MySQL are built on mysql-common-8.0.x which conflicts on systems with MariaDB installed:

Servers that have perl-DBD-MySQL already installed can fail nightly updates.
Seems to be related to REHL upstream: https://issues.redhat.com/browse/RHEL-88746

However, if that's the case than the only thing we can do is ban those packages/remove them always when MariaDB is installed,. Still, if the user has specifically installed those for scripts of their own that involve a remote mysql server, those are instantly broken by such a change we make there.

0000592: LTP memcontrol03 fails with “TBROK: tst_checkpoint_wait() ETIMEDOUT (110)” on AlmaLinux 9 / cgroup v2 — Is this expected behavio

Thu, 11 Dec 2025 06:07:14 +0000

Hello Community,

I am running LTP (Linux Test Project) on AlmaLinux 9.6 running on Azure (kernel using cgroup v2 unified hierarchy).
One of the tests, controllers/memcontrol03, consistently results in:

TBROK: tst_checkpoint_wait(1, 10000) failed: ETIMEDOUT (110)

What I have verified so far

The system correctly exposes cgroup v2 memory controller files:

memory.current
memory.max
memory.events
memory.stat
memory.reclaim
memory.swap.*

The test appears to wait for a memory event notification that never occurs.

According to the documentation, memcontrol03 relies on cgroup v1-style memory events, which are not generated under cgroup v2.

My understanding

From reading kernel documentation and test code:

cgroup v2 no longer provides legacy memory event notifications expected by memcontrol03
→ https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#memory-controller

memcontrol03 waits inside tst_checkpoint_wait() for an event that v2 systems do not emit
→ leading to the timeout and TBROK.

Questions for the community

Is this TBROK result expected for all cgroup v2 systems?

Is memcontrol03 officially considered incompatible with cgroup v2?

Should this test be skipped/marked as BROKEN on any distro using cgroup v2 (RHEL9/AL9/Fedora)?

Is there any known workaround, or is the correct approach to exclude the test?

Additional context

Same behavior across multiple AlmaLinux 9 VMs on Azure.

No OS/kernel defects observed; other memory controller tests run normally.

Logs show that the event never occurs within the 10-second window.

I would appreciate clarification or official guidance from LTP maintainers or anyone familiar with memory controller tests on cgroup v2.

Thank you!

0000589: Does AlmaLinux 9.6 officially support Azure Gen2 (UEFI) VMs, vTPM / Trusted Launch and Gen2 VHD preparation?

Wed, 03 Dec 2025 06:31:46 +0000

Hi all — quick technical questions and a request for guidance.

Does AlmaLinux 9.6 officially support Azure Generation 2 (UEFI) VMs (including booting and normal operation)?

Is vTPM exposure / Trusted Launch (vTPM + Secure Boot) supported for AlmaLinux 9.6 on Azure? If so, any known caveats?

Is the official AlmaLinux 9.6 Marketplace image Gen1 only, or are Gen2 Marketplace images available?

If uploading our own Gen2-compatible VHD, we hit an Azure error about an invalid VHD footer (cookie value / 'conectix'). Can someone confirm the correct VHD preparation/conversion steps for Gen2 Linux images that are accepted by Azure (fixed VHD, page-blob, footer cookie, UEFI, etc.)? Any official docs or known workarounds would be appreciated.

Context / what we tried:

We converted a qcow2 image to .vhd and uploaded, but Azure rejected it with an invalid VHD footer / cookie message. We want the recommended conversion steps/commands for a Gen2 (UEFI) Linux VHD that will upload and create a Gen2 VM (and be eligible for Trusted Launch).

Thanks — any links to AlmaLinux or Microsoft docs, Marketplace guidance, or step-by-step commands would be great.

0000588: [Feature] Include libnvidia-container repo in almalinux-release-nvidia-driver

Mon, 01 Dec 2025 15:29:11 +0000

The nvidia container integration is handy for prototyping and testing various gpu workloads. It would be handy if, in addition to the cuda repo, the libcontainer repo was included.

0000587: Unable to install perl-DBD-MySQL-4.053 in a MySQL 8.4 (libmysqlclient.so.24)

Thu, 27 Nov 2025 02:47:27 +0000

Unable to install perl-DBD-MySQL-4.053 in a MySQL 8.4 (libmysqlclient.so.24) environment
due to a dependency on libmysqlclient.so.21.

0000586: Package ncurses-static-6.1-9.20180224.el8.ppc64le.rpm is not signed in AlmaLinux 8.6

Wed, 26 Nov 2025 23:28:12 +0000

The package ncurses-static-6.1-9.20180224.el8.ppc64le.rpm is not signed in AlmaLinux 8.6

0000555: Please add support for AWS EC2 G6f & Gr6f instances in AWS Marketplace: AlmaLinux-10

Wed, 26 Nov 2025 15:13:27 +0000

Please add support for AWS EC2 G6f & Gr6f instances in AWS Marketplace

AWS announcement: https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-ec2-g6f-instances-fractional-gpus/

0000554: Please add support for AWS EC2 G6f & Gr6f instances in AWS Marketplace: AlmaLinux-9

Wed, 26 Nov 2025 15:13:17 +0000

Please add support for AWS EC2 G6f & Gr6f instances in AWS Marketplace

AWS announcement: https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-ec2-g6f-instances-fractional-gpus/

0000553: Add support for AWS EC2 G6f & Gr6f instances in AWS Marketplace

Wed, 26 Nov 2025 15:13:06 +0000

Please add support for AWS EC2 G6f & Gr6f instances in AWS Marketplace

AWS announcement: https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-ec2-g6f-instances-fractional-gpus/

0000356: Suggestion to provide public debuginfod service for AlmaLinux

Tue, 25 Nov 2025 23:31:47 +0000

debuginfod is a very nice feature where gdb can automatically fetch debuginfo data over HTTP from a central server or a local mirror. See https://fedoraproject.org/wiki/Debuginfod

It would be very convenient if AlmaLinux could provide a debuginfod server for all it's RPMs, much like CentOS does with https://debuginfod.centos.org/