openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

CNV#23697: ARM support

Browse Source
This commit is contained in:
Pan Ousley
2025-08-11 16:22:54 -04:00
committed by openshift-cherrypick-robot
parent 8a4c8420cc
commit 00822e30cf
2 changed files with 26 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/virt-networking-wizard-fields-web.adoc
View File

@@ -17,7 +17,7 @@
|Model
|Indicates the model of the network interface controller. Supported values are *e1000e* and *virtio*.
On {ibm-z-name}, the only valid NIC model option is *virtio*. *e1000e* is not supported.
For {ibm-z-name} (`s390x`) and ARM64 (`arm64`) systems, use the *virtio* NIC model option. The *e1000e* model is not supported on these architectures.
|Network
|List of available network attachment definitions.

29
virt/install/preparing-cluster-for-virt.adoc
View File

@@ -19,6 +19,8 @@ You can use the following platforms with {VirtProductName}:
* On-premise bare metal servers. See xref:../../installing/installing_bare_metal/preparing-to-install-on-bare-metal.adoc#virt-planning-bare-metal-cluster-for-ocp-virt_preparing-to-install-on-bare-metal[Planning a bare metal cluster for {VirtProductName}].
* Bare metal clusters installed on ARM64-based (`arm64`, also known as `aarch64`) systems.
//* {ibm-cloud-name} Bare Metal Servers. See link:https://access.redhat.com/articles/6738731[Deploy {VirtProductName} on {ibm-cloud-name} Bare Metal nodes].
//+
//--
@@ -113,6 +115,25 @@ include::modules/virt-aws-bm.adoc[leveloffset=+2]
* xref:../../virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc#virt-connecting-vm-to-ovn-secondary-network[Connecting a virtual machine to an OVN-Kubernetes secondary network]
* xref:../../virt/vm_networking/virt-exposing-vm-with-service.adoc#virt-exposing-vm-with-service[Exposing a virtual machine by using a service]
[id="arm-compatibility_{context}"]
=== ARM64 compatibility
Using {VirtProductName} on an {product-title} cluster installed on an ARM64 system is generally available (GA).
Before using {VirtProductName} on an ARM64-based system, consider the following limitations:
Operating system::
* Only Linux-based guest operating systems are supported.
* All virtualization limitations for {op-system-base} also apply to {VirtProductName}. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/assembly_feature-support-and-limitations-in-rhel-9-virtualization_configuring-and-managing-virtualization#how-virtualization-on-arm-64-differs-from-amd64-and-intel64_feature-support-and-limitations-in-rhel-9-virtualization[How virtualization on ARM64 differs from AMD64 and Intel 64] in the {op-system-base} documentation.
Live migration::
* Live migration is *not supported* on ARM64-based {product-title} clusters.
* Hotplug is not supported on ARM64-based clusters because it depends on live migration.
VM creation::
* {op-system-base} 10 supports instance types and preferences, but not templates.
* {op-system-base} 9 supports templates, instance types, and preferences.
// Hiding in ROSA/OSD - todo: double check this
ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
[id="ibm-z-linuxone-compatibility_{context}"]
@@ -218,10 +239,10 @@ If your worker nodes have different CPUs, live migration failures might occur be
See xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-configuring-required_nodes-scheduler-node-affinity[Configuring a required node affinity rule] for details.
====
* Support for AMD and Intel 64-bit architectures (x86-64-v2).
* Support for Intel 64 or AMD64 CPU extensions.
* Intel VT or AMD-V hardware virtualization extensions enabled.
* NX (no execute) flag enabled.
* Supports AMD64, Intel 64-bit (x86-64-v2), {ibm-z-name} (`s390x`), or ARM64-based (`arm64` or `aarch64`) architectures and their respective CPU extensions.
* Intel VT-x, AMD-V, or ARM virtualization extensions are enabled, or `s390x` virtualization support is enabled.
* NX (no execute) flag is enabled.
* If you use `s390x` architecture, the xref:../../virt/managing_vms/advanced_vm_management/virt-configuring-default-cpu-model.adoc#virt-configuring-default-cpu-model[default CPU model] is set to `gen15b`.
[id="os-requirements_preparing-cluster-for-virt"]
=== Operating system requirements