Rocky Linux
Rocky Linux 8.3
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.3 x64 | RHEL | 8.3 | x64 | kvm, kvm_virtio | 1.0 |
Limitation: The template is not compatible with Xen.
Rocky Linux 8.3 with kernel-ml
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux kernel_ml x64 | RHEL | 8.3 | x64 | xen, kvm, kvm_virtio | 1.0 |
- Note: 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
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.4 x64 | RHEL | 8.4 | x64 | kvm, kvm_virtio | 1.0-1.1 |
- Limitation: The template isn't compatible with Xen.
Rocky Linux 8.4 with kernel-ml
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.4 kernel_ml x64 | RHEL | 8.4 | x64 | xen, kvm, kvm_virtio | 1.0-1.1 |
- Note: 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
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.5 х64 | RHEL | 8.4 | x64 | kvm, kvm_virtio | 1.0-1.1 |
Limitation: The template isn't compatible with Xen.
Rocky Linux 8.5 with kernel-ml
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.5 kernel_ml х64 | RHEL | 8.5 | x64 | xen, kvm, kvm_virtio | 1.0-1.4 |
- Note: 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
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.6 x64 | RHEL | 8.6 | x64 | kvm, kvm_virtio | 1.0-1.5 |
- Limitation: The template isn't compatible with Xen.
Rocky Linux 8.6 with kernel-ml
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.6 kernel_ml x64 | RHEL | 8.6 | x64 | xen, kvm, kvm_virtio | 1.0-1.5 |
- Note:
- Running 6.x kernel-ml version.
- 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 Release 8.7 (Green Obsidian)
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.7 x64 | RHEL | 8.7 | x64 | kvm, kvm_virtio | 1.0 - 1.4 |
- Limitation: The template isn't compatible with Xen.
Rocky Linux Release 8.7 (Green Obsidian) with kernel-ml
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.7 kernel_ml x64 | RHEL | 8.7 | x64 | xen, kvm, kvm_virtio | 1.0 - 1.4 |
- Note: Running 6.x kernel-ml version.
- 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 release 8.8 (Green Obsidian)
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.8 | RHEL | 8.8 | x64 | xen, kvm, kvm_virtio | 1.0 |
- Limitation: The template isn't compatible with Xen.
Rocky Linux release 8.8 (Green Obsidian) with kernel-ml
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 8.8 kernel_ml x64 | RHEL | 8.8 | x64 | xen, kvm, kvm_virtio | 1.0 |
- Note: Running 6.x kernel-ml version.
- 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
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 9.0 x64 | RHEL | 9.0 | x64 | kvm, kvm_virtio | 1.0-1.2 |
- Issues:
network-scriptsnetworking management has been deprecated in EL9.NetworkManageris now used. It isn't supported by OnApp.
Because of that:- Assigning multiple IP addresses won't work.
Changing the Primary IP Address with rebuilding the 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.
Rocky Linux 9.1
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 9.1 x64 | RHEL | 9.1 | x64 | kvm, kvm_virtio | 1.0 - 1.4 |
- Issues:
network-scriptsnetworking management has been deprecated in EL9.NetworkManageris now used. It isn't supported by OnApp.
Because of that:- Assigning multiple IP addresses won't work.
Changing the Primary IP Address with rebuilding the network (via OnApp UI) will require manual actions in VM's main console:
# /etc/rc.d/init.d/el9NM2onapp start # nmcli dev reapply eth0
- Limitation:
- The template isn't compatible with Xen.
- The VM 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.
Rocky Linux 9.2 (Blue Onyx)
| Template label | Operating system | OS release | OS arch | Virtualization | Version |
| Rocky Linux 9.2 x64 | RHEL | 9.1 | x64 | kvm, kvm_virtio | 1.0 - 1.4 |
- Issues:
network-scriptsnetworking management has been deprecated in EL9.NetworkManageris now used. It isn't supported by OnApp.
Because of that:- Assigning multiple IP addresses won't work.
Changing the Primary IP Address with rebuilding the network (via OnApp UI) will require manual actions in VM's main console:
# /etc/rc.d/init.d/el9NM2onapp start # nmcli dev reapply eth0
- Limitation:
- The template isn't compatible with Xen.
- The VM 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.