RHEL AI 3.6 early access moves its base to RHEL 9.8 EUS
The unsupported preview also advances the inference stack, adds a separate vLLM-Omni technology-preview image and narrows the supported upgrade path.
Red Hat has published the first early-access release of Red Hat Enterprise Linux AI 3.6, moving the product’s operating-system base from RHEL 9.6 to RHEL 9.8 Extended Update Support and refreshing its inference runtime. Red Hat labels the build unsupported and unsuitable for production, making it a test target rather than a deployment recommendation. The 3.6 early-access release notes document the changes and limitations.
A new base and a narrower upgrade gate
The base-image change matters for teams that validate drivers, accelerators and deployment automation against a specific RHEL minor line. The same release notes say an in-place upgrade to 3.6 early access is supported from RHEL AI 3.0 or later, but not directly from RHEL AI 1.5. That leaves older installations needing an intermediate migration plan before they can evaluate the preview.
The bundled inference stack moves to vLLM 0.26.0, while the Red Hat AI Inference component is identified as 3.6.0-fast.1. Those version shifts give platform teams a concrete compatibility target for model, kernel and accelerator testing, but the early-access status means the results should not be treated as a production support commitment.
Multimodal serving arrives as a separate preview
RHEL AI 3.6 also introduces vLLM-Omni as a technology preview. Red Hat packages it in a separate CUDA image based on vLLM-Omni 0.26.1 rather than folding it into the standard inference image. That separation is operationally useful: teams can evaluate multimodal serving without quietly changing the runtime used by existing text-model deployments, while still keeping the preview outside production estates.
Another technology preview exposes Anthropic cache-token information. This can help operators inspect cache behavior and cost-related token accounting in compatible workflows, but it carries the same preview caveat.
Hardware paths remain uneven. Red Hat says the ROCm image does not include the Model Optimization Toolkit, so AMD GPU evaluators should not assume feature parity with the CUDA path when designing 3.6 tests.
What platform teams should do
The practical next step is a disposable validation environment: confirm the RHEL 9.8 EUS base against local security controls, test the supported upgrade route from a 3.x installation, and evaluate the standard and Omni images separately. Production clusters should remain on supported releases until Red Hat moves these capabilities beyond early access.
sources
- Red Hat Enterprise Linux AI 3.6 early access release notesdocs.redhat.com
comments · 0