AlmaLinux Templates

AlmaLinux Release 8.3 x64


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux x64

RHEL

8.3

x64

kvm, kvm_virtio

1.0 - 1.3





  • Issues: After operating system upgrade (with 'yum update') and before reboot, please check and modify GRUB_ENABLE_BLSCFG option's value (set it into 'false',) in GRUB2 boot loader's default configuration file /etc/default/grub. Then generate new GRUB2 boot loader's main config with:

    # grub2-mkconfig -o /boot/grub2/grub.cfg

    Reboot the system (if required).

  • Limitation: The template isn't compatible with Xen

AlmaLinux Release 8.3 x64 (kernel_ml)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.3 kernel_ml x64

RHEL

8.3

x64

xen, kvm, kvm_virtio

1.0 - 1.1





  • Issues: After operating system upgrade (with 'yum update') and before reboot, please check and modify GRUB_ENABLE_BLSCFG option's value (set it into 'false',) in GRUB2 boot loader's default configuration file /etc/default/grub. Then generate new GRUB2 boot loader's main config with:

    # grub2-mkconfig -o /boot/grub2/grub.cfg

    Reboot the system (if required).

  • Limitation: Using the kernel_ml may expose your system to security, performance, and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. These packages are not signed for SecureBoot.


AlmaLinux Release 8.4 (Electric Cheetah)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.4 x64

RHEL

8.4

x64

kvm, kvm_virtio

1.0 - 1.3





  • Issues: After operating system upgrade (with 'yum update') and before reboot, please check and modify GRUB_ENABLE_BLSCFG option's value (set it into 'false',) in GRUB2 boot loader's default configuration file /etc/default/grub. Then generate new GRUB2 boot loader's main config with:

    # grub2-mkconfig -o /boot/grub2/grub.cfg

    Reboot the system (if required).

  • Limitation: The template isn't compatible with Xen.

AlmaLinux Release 8.4 x64 (kernel_ml)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.4 kernel_ml x64

RHEL

8.4

x64

xen, kvm, kvm_virtio

1.0 - 1.3





  • Issues: After operating system upgrade (with 'yum update') and before reboot, please check and modify GRUB_ENABLE_BLSCFG option's value (set it into 'false',) in GRUB2 boot loader's default configuration file /etc/default/grub. Then generate new GRUB2 boot loader's main config with:

    # grub2-mkconfig -o /boot/grub2/grub.cfg

    Reboot the system (if required).

  • Limitation: Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. These packages are not signed for SecureBoot.


AlmaLinux Release 8.5 (Arctic Sphynx)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.5 x64 

RHEL

8.5

x64

kvm, kvm_virtio

1.0 - 1.3

  • Issues: After operating system upgrade (with 'yum update') and before reboot, please check and modify GRUB_ENABLE_BLSCFG option's value (set it into 'false',) in GRUB2 boot loader's default configuration file /etc/default/grub. Then generate new GRUB2 boot loader's main config with:

    # grub2-mkconfig -o /boot/grub2/grub.cfg

    Reboot the system (if required).

  • Limitation: The template isn't compatible with Xen.


AlmaLinux Release 8.5 x64 (kernel_ml)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.5 kernel_ml x64

RHEL

8.5

x64

kvm, kvm_virtio

1.0 - 1.2

  • Issues: After operating system upgrade (with 'yum update') and before reboot, please check and modify GRUB_ENABLE_BLSCFG option's value (set it into 'false',) in GRUB2 boot loader's default configuration file /etc/default/grub. Then generate new GRUB2 boot loader's main config with:

    # grub2-mkconfig -o /boot/grub2/grub.cfg

     Reboot the system (if required).

  • Limitation: Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. These packages are not signed for SecureBoot.


AlmaLinux Release 8.6 (Sky Tiger)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.6 x64

RHEL

8.6

x64

kvm, kvm_virtio

1.0 - 1.4



  • Limitation: The template isn't compatible with Xen.

AlmaLinux Release 8.6 x64 (kernel_ml)


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 8.6 kernel_ml x64

RHEL

8.6

x64

xen, kvm, kvm_virtio

1.0 - 1.4



  • Limitation: Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. These packages are not signed for SecureBoot.

AlmaLinux 9.0


Template label

Operating system

OS release

OS arch

Virtualization

Version

AlmaLinux 9.0 x64

RHEL

9.0

x64

kvm, kvm_virtio

1.0 - 1.2

  • Issues: Network-scripts networking management has been deprecated in EL9. NetworkManager is now used. It isn't supported by OnApp.
    Because of that:
    - Assigning multiple IP addresses won't work.
    - Changing Primary IP Address with "Rebuild Network" (via OnApp UI) will require manual actions in VS's main console:

    # /etc/rc.d/init.d/el9NM2onapp start
    # nmcli dev reapply eth0
  • Limitation:
    - The template isn't compatible with Xen.
    - Packages update is disabled via:

    /etc/yum.conf with setting exclude=*

    The reason is that glibc-2.34-20 includes a fix to more reliably detect CPU compatibility. See the bug at https://bugzilla.redhat.com/show_bug.cgi?id=2040657. Such detection generates the following inside guest:
    "Fatal glibc error: CPU does not support x86-64-v2".

To configure the correct CPU model, refer to Configure CPU Model.