live wire
▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel
upstreambeat.ai
newsPLATFORM

OpenShift Virtualization 4.22 earns NVIDIA’s HGX hypervisor certification

The validation gives platform teams a common Kubernetes control plane for GPU-backed virtual machines and containerized AI workloads, but Red Hat still advises workload-specific testing.

By The News Desk· Oct 23, 2026the quick take — two AI hosts go live when you do

NVIDIA now lists Red Hat OpenShift Container Platform 4.22 with OpenShift Virtualization 4.22 as a certified hypervisor platform for Hopper SXM systems. The accessible NVIDIA certification record replaces the Red Hat announcement that later disappeared, and it narrows the claim to a specific platform version, hardware track and validation scope.

What the certification covers

NVIDIA’s x86 certification track is scoped to NVSwitch-based, eight-GPU Hopper SXM systems, covering NVIDIA HGX and DGX platforms. It requires two phases: a single-node test with one eight-GPU virtual machine using full GPU and NIC passthrough, followed by a multi-node test with two eight-GPU virtual machines on two identical Hopper nodes.

The certification table names the covered platform precisely: Red Hat OpenShift Container Platform 4.22 with OpenShift Virtualization 4.22. It does not state that all OpenShift versions, GPU models or virtualization configurations inherit the result. NVIDIA also directs readers to its AI Enterprise Infrastructure Support Matrix for currently supported component versions.

That specificity matters for platform teams. The listing validates a demanding passthrough topology, but it is not a blanket performance guarantee for every virtualized AI workload.

How GPU workloads fit into OpenShift Virtualization

NVIDIA’s OpenShift documentation describes OpenShift Virtualization as KubeVirt-based VM management inside Kubernetes. It allows virtual machines and containers to coexist in one cluster, while NVIDIA’s GPU Operator can provision worker nodes for either GPU-accelerated containers or GPU-accelerated virtual machines.

Those modes are not interchangeable on a single worker. NVIDIA documents three node workload labels—container, vm-passthrough and vm-vgpu—and says one worker runs one of those GPU workload types, not a mixture. The required software also differs: containers use the data-center driver and container toolkit; passthrough VMs use vfio-pci; and virtual-GPU deployments require the NVIDIA vGPU Manager.

For passthrough and vGPU, administrators can choose GPU Operator-managed components or OpenShift Virtualization’s native procedures. NVIDIA warns that GPU Operator operands must be disabled on nodes that use OpenShift Virtualization’s native PCI passthrough path to avoid conflicts.

What platform teams should test

Organizations evaluating the certified configuration should first confirm that their target matches the listing: OpenShift Container Platform and OpenShift Virtualization 4.22 on Hopper SXM infrastructure. They should then reproduce the relevant topology—single- or multi-node, full GPU and NIC passthrough—and validate their own storage, networking and model-serving behavior.

Operational tests matter as much as throughput. Teams should verify node labeling, driver ownership, device discovery, upgrades and failure recovery before consolidating containerized AI services and GPU-backed VMs. The certification is useful evidence for the named stack; the production decision still depends on whether that stack’s explicit constraints fit the workload.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.