1.2. Supported limits


Refer to tested object maximums when planning your environment for your specific use case, and consider all factors that can impact cluster scaling. For information options that impact performance, see the "OpenShift Virtualization - Tuning & Scaling Guide" in the Red Hat Knowledgebase.

1.2.1. Tested maximums for OpenShift Virtualization

Maximums are based on a single cluster of the largest possible size for a OpenShift Virtualization 4.x environment. Approaching the maximum values can reduce performance and increase latency. Consider using multiple smaller clusters if possible to improve performance.

1.2.1.1. Virtual machine maximums

Maximums apply to virtual machines (VMs) running on OpenShift Virtualization and are subject to the limits specified in "Virtualization limits for Red Hat Enterprise Linux with KVM".

Expand
Objective (per VM)Tested limitTheoretical limit

Virtual CPUs

255 vCPUs

255 vCPUs

Memory

6 TB

16 TB

Single disk size

100 TB

100 TB

Hot-pluggable disks

255 disks

N/A

참고

Each VM must have at least 512 MB of memory. The fstype in the guest operating system (OS) must support the maximum limits. Do not use preallocation in data volumes that are larger than 99 TB.

1.2.1.2. Host maximums

The following maximums apply to the OpenShift Container Platform hosts used for OpenShift Virtualization.

Expand
Objective (per host)Tested limitTheoretical limit

Logical CPU cores or threads

Same as Red Hat Enterprise Linux (RHEL)

N/A

RAM

Same as RHEL

N/A

Simultaneous live migrations

Defaults to 2 outbound migrations per node, and 5 concurrent migrations per cluster

Depends on NIC bandwidth

Live migration bandwidth

No default limit

Depends on NIC bandwidth

1.2.1.3. Cluster maximums

The following maximums apply to objects defined in OpenShift Virtualization.

Expand
Objective (per cluster)Tested limitTheoretical limit

Number of attached PVs per node

N/A

CSI storage provider dependent

Maximum PV size

N/A

CSI storage provider dependent

Hosts

500 hosts (100 or fewer recommended) [1]

Same as OpenShift Container Platform

Defined VMs

10,000 VMs [2]

Same as OpenShift Container Platform

  1. If you use more than 100 nodes, consider using Red Hat Advanced Cluster Management (RHACM) to manage multiple clusters instead of scaling out a single control plane. Larger clusters add complexity, require longer updates, and depending on node size and total object density, they can increase control plane stress.

    Using multiple clusters can be beneficial in areas like per-cluster isolation and high availability.

  2. The maximum number of VMs per node depends on the host hardware and resource capacity. It is also limited by the following parameters:

    • Settings that limit the number of pods that can be scheduled to a node. For example: maxPods.
    • The default number of KVM devices. For example: devices.kubevirt.io/kvm: 1k.
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

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

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

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

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동