RHEL AI 3.5 moves the appliance forward—and leaves 1.5 upgrades behind
The GA refresh packages vLLM 0.24 and new accelerator stacks, but operators on RHEL AI 1.5 cannot upgrade directly.
Red Hat released Red Hat Enterprise Linux AI 3.5 on September 22 through product-enhancement advisories, while the product documentation identifies the generally available image version as 3.5.0. The release moves the appliance to newer inference, optimization and accelerator components, but it also creates a hard planning boundary for operators still on the 1.5 line. (Red Hat advisory; release notes)
What changed
RHEL AI 3.5.0 is published as bootc images for general CUDA and ROCm deployments and for AWS, Azure and Google Cloud variants; Red Hat also lists a CUDA disk image as GA. The Gaudi bootc image remains Technology Preview. (release notes)
The release packages Red Hat AI Inference 3.5.0 with upstream vLLM 0.24.0. It also packages Red Hat AI Model Optimization Toolkit 3.5.0 with upstream LLM Compressor 0.12.0. (release notes)
The accelerator stack advances to AMD ROCm 7.14 using the TheRock framework, NVIDIA CUDA 13.0.2 and Intel Gaudi software 1.24.1-482. Red Hat specifies NVIDIA driver 580.173.02 as the minimum for CUDA 13.0.2; Gaudi support remains Technology Preview. (release notes)
Who it affects
Operators on RHEL AI 3.0 or later can move through the supported 3.x path to 3.5. Red Hat explicitly says there is no direct upgrade from RHEL AI 1.5 to 3.5, so 1.5 estates need a migration or replacement plan rather than treating this as an ordinary in-place update. (release notes)
The accelerator choice also changes the included toolset. Red Hat says the ROCm bootc image does not contain the Model Optimization Toolkit because that toolkit is not supported on AMD ROCm accelerators. (release notes)
What to do
Before deploying, select the image that matches the target cloud and accelerator, verify that NVIDIA systems meet the minimum driver level, and treat the Gaudi image as non-production Technology Preview software. Operators on 1.5 should plan a redeployment or staged migration; operators on 3.0 and later should follow the documented intermediate upgrade path. (release notes)
sources
- Red Hat Enterprise Linux AI 3.5 release notesdocs.redhat.com
- RHEA-2026:70190 — Red Hat Enterprise Linux AIaccess.redhat.com
comments · 0