I'm closing the ticket as the problem has been addressed once again.

I am re-opening this issue because the problem occurs in RHEL 9.5 and also RHEL 9.6.
I recently installed fresh RHEL 9.6 – RHEL-9.6.0-20250121.2-aarch64-dvd1.iso – and when I try to select the 64k page size, I get "Problem: package kmod-kvdo... from anaconda conflicts with kernel-64k provided by kernel-64k... from anaconda – conflicting requests".
At a request of gcase, I also tried RHEL 9.5 – RHEL-9.5.0-20241124.2-aarch64-dvd1.iso – which also had the same problem. I get the same "Error checking software selection", ultimately forcing selection of 4k page size.
Doc written by gcase, with lots of additional info: https://docs.google.com/document/d/1spAGsuB1birkol7I0iSvDgI0OYhN9huE1zEqYq2oB2k/edit?usp=sharing

Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (kmod-kvdo bug fix and enhancement update), and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:2405

An upgrade is a move from one major version of RHEL to another, such as from RHEL 8.8 to RHEL 9.2. An update, on the other hand, is a move from one minor version of RHEL to another, such as from RHEL 9.2 to RHEL 9.3.

Currently, there is no RHEL 9 to RHEL 10 upgrade because RHEL 10 doesn't exist yet, so you can't perform an upgrade on any version of RHEL 9. Do you mean to say 'update' here instead of 'upgrade'?

From slegendr@redhat.com - 

RN need to be updated: 

The existing release note is no longer applicable, as the installation and boot issue will be resolved through a separate ticket. However, an upgrade issue for 64k kernels will remain when going from RHEL-9.3 to 9.x. Upgrades will be broken when kernel-64k and kmod-kvdo are both present. The solution is to remove kmod-kvdo prior to attempting to upgrade so that it and its 4k kernel dependencies are removed.

jstodola@redhat.com We are working on getting VDO accepted into the upstream kernel. Once it is included in the upstream kernel, this will no longer be an issue. As such, adding another build of kmod-kvdo explicitly for the 64k kernel is not feasible. The additional maintenance burden would be significant.

In the meantime, I am modifying the spec file so that kernel-64k is listed as a conflict for kmod-kvdo. This will prevent vdo, kmod-kvdo and the associated dependencies from installing on 64k-enabled hosts, thus correcting the boot issue.

Susan LeGendre-McGhee mentioned this issue in a merge request of Red Hat / centos-stream / rpms / kmod-kvdo on branch resolve_rhel_8354:

Revert previous changes and add kernel-64k as a conflict.

slegendr@redhat.com, it is possible to select the minimal package set interactively in the installer. It is on the same screen as the 4k/64k kernel selection, see the installation guide

Pre-selecting the minimal package set when the user chose to install the 64k kernel is just a workaround, since the user could immediately select another package set or try to install and use vdo/kmod-kvdo later on the installed system.

IMO, the correct fix is to provide a kernel module compatible with the 64k kernel.

Susan LeGendre-McGhee mentioned this issue in a commit of Red Hat / centos-stream / rpms / kmod-kvdo on branch resolve_rhel_8354:

Modify to accommodate kernel-64k packages.

Susan LeGendre-McGhee mentioned this issue in a merge request of Red Hat / centos-stream / rpms / kmod-kvdo on branch resolve_rhel_8354:

Modify to accommodate kernel-64k packages.