Rocky Linux Templates

Rocky Linux 8.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 is not compatible with Xen.

Rocky Linux 8.3 (kernel_ml)

• 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.

Rocky Linux 8.4

• 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.

Rocky Linux 8.4 (kernel_ml)

• 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.

Rocky Linux 8.5

• 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.

Rocky Linux 8.5 (kernel_ml)

• 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.

Rocky Linux 8.6

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

Rocky Linux 8.6 (kernel_ml)

• 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.

Rocky Linux 9.0

• 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.
  • The VS based on the template should be configured with the correct CPU model.
    The reason is that glibc-2.34-20 includes a fix to more reliable detect CPU compatibility. See the bug information at https://bugzilla.redhat.com/show_bug.cgi?id=2040657. Such detection generates the following inside the guest:
    "Fatal glibc error: CPU does not support x86-64-v2".
    To configure the correct CPU model, refer to <Configure CPU Model>.