4장. Installing


4.1. Preparing your cluster for OpenShift Virtualization

Review platform compatibility information before you install OpenShift Virtualization. For detailed system requirements, see "Hardware, software, and operational requirements" in the Additional resources section.

4.1.1. Compatible platforms

OpenShift Virtualization supports bare-metal servers, ARM64-based systems, and IBM Z® or IBM® LinuxONE systems in logical partitions.

Compatible platforms
  • On-premise bare-metal servers. For more information, see "Planning a bare-metal cluster for OpenShift Virtualization" in the Additional resources section.
  • Bare-metal clusters installed on ARM64-based (arm64, also known as aarch64) systems.
  • IBM Z® or IBM® LinuxONE (s390x architecture) systems where an OpenShift Container Platform cluster is installed in logical partitions (LPARs). For more information, see "Preparing to install on IBM Z and IBM LinuxONE" in the Additional resources section.

4.1.2. Cloud platforms

OpenShift Virtualization is compatible with various public cloud platforms. Each platform has specific storage options available.

Expand
VendorStatusStorageResources

Amazon Web Services (AWS)

GA

  • Elastic Block Store (EBS)
  • Red Hat OpenShift Data Foundation (ODF)
  • Portworx
  • FSx (NetApp)
  • See "Installing a cluster on AWS with customizations" in the Additional resources section.

Red Hat OpenShift Service on AWS (ROSA)

GA

  • EBS
  • Portworx
  • FSx (Q3)
  • ODF

Oracle Cloud Infrastructure (OCI)

GA

  • OCI native storage

Azure Red Hat OpenShift (ARO)

GA

  • ODF

Google Cloud

GA, as of OpenShift Virtualization 4.21.1

  • Google Cloud native storage
  • Google Cloud NetApp Volumes (GCNV); requires OpenShift Virtualization 4.21.2 or later

Bare-metal instances or servers offered by other cloud providers are not supported.

작은 정보

For platform-specific networking information, see "Networking overview" in the Additional resources section.

4.1.3. OpenShift Virtualization on AWS bare metal

You can run OpenShift Virtualization on an Amazon Web Services (AWS) bare metal OpenShift Container Platform cluster.

참고

OpenShift Virtualization is also supported on Red Hat OpenShift Service on AWS (ROSA) Classic clusters, which have the same configuration requirements as AWS bare-metal clusters.

4.1.4. ARM64 compatibility

OpenShift Virtualization on ARM64 systems is generally available (GA) with specific limitations for operating systems and live migration.

Before using OpenShift Virtualization on an ARM64-based system, consider the following limitations:

Operating system
Live migration
  • Live migration is not supported on ARM64-based OpenShift Container Platform clusters.
  • Hotplug is not supported on ARM64-based clusters because it depends on live migration.
VM creation
  • RHEL 10 supports instance types and preferences, but not templates.
  • RHEL 9 supports templates, instance types, and preferences.

4.1.5. IBM Z and IBM LinuxONE compatibility

You can use OpenShift Virtualization in an OpenShift Container Platform cluster that is installed in logical partitions (LPARs) on an IBM Z® or IBM® LinuxONE (s390x architecture) system.

Some features are not currently available on s390x architecture, while others require workarounds or procedural changes. These lists are subject to change.

Currently unavailable features

The following features are currently not available on s390x architecture:

  • Memory hot plugging and hot unplugging
  • Node Health Check Operator
  • SR-IOV Operator
  • PCI passthrough
  • OpenShift Virtualization cluster checkup framework
  • OpenShift Virtualization on a cluster installed in FIPS mode
  • IPv6
  • IBM® Storage scale
  • Hosted control planes for OpenShift Virtualization
  • VM pages using HugePages

    The following features are not applicable on s390x architecture:

  • virtual Trusted Platform Module (vTPM) devices
  • UEFI mode for VMs
  • USB host passthrough
  • Configuring virtual GPUs
  • Creating and managing Windows VMs
  • Hyper-V
Functionality differences

The following features are available for use on s390x architecture but function differently or require procedural changes:

  • When deleting a virtual machine by using the web console, the grace period option is ignored. For more information, see "Deleting a virtual machine by using the web console" in the Additional resources section.
  • When configuring the default CPU model, the spec.defaultCPUModel value is "gen15b" for an IBM Z cluster. For more information, see "Configuring the default CPU model" in the Additional resources section.
  • When configuring a downward metrics device, if you use a VM preference, the spec.preference.name value must be set to rhel.9.s390x or another available preference with the format *.s390x. For more information, see "Configuring a downward metrics device" in the Additional resources section.
  • When creating virtual machines from instance types, you are not allowed to set spec.domain.memory.maxGuest because memory hot plugging is not supported on IBM Z®. For more information, see "Creating virtual machines from instance types" in the Additional resources section.
  • Prometheus queries for VM guests could have inconsistent outcome in comparison to x86.

4.1.6. Important considerations for any platform

Before installing OpenShift Virtualization, note key considerations about installation methods, storage, IPv6, and FIPS mode.

Installation method considerations
You can use any installation method, including user-provisioned, installer-provisioned, or Assisted Installer, to deploy OpenShift Container Platform. However, the installation method and the cluster topology might affect OpenShift Virtualization functionality, such as snapshots or live migration. For more information about live migration, see "Hardware, software, and operational requirements" in the Additional resources section.
Red Hat OpenShift Data Foundation
If you deploy OpenShift Virtualization with Red Hat OpenShift Data Foundation, you must create a dedicated storage class for Windows virtual machine disks. For more information, see "Optimizing ODF PersistentVolumes for Windows VMs" in the Additional resources section.
IPv6
OpenShift Virtualization support for single-stack IPv6 clusters is limited to the OVN-Kubernetes localnet and Linux bridge Container Network Interface (CNI) plugins.
중요

{FeatureName} is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

FIPS mode
If you install your cluster in FIPS mode, no additional setup is required for OpenShift Virtualization. For more information, see "Installing a FIPS-compliant cluster" in the Additional resources section.

4.1.7. Object maximums

Consider tested object maximums for both OpenShift Container Platform and OpenShift Virtualization when planning your cluster.

OpenShift Container Platform
See "OpenShift Container Platform object maximums" in the Additional resources section.
OpenShift Virtualization
See "OpenShift Virtualization supported limits" in the Additional resources section.
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동