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-11965 for defect 1959287 CPU vendors

Browse Source 
CNV-11965 for defect 1959287 CPU vendors

CNV-11965 for defect 1959287 CPU vendors

CNV-11965 for defect 1959287 CPU vendors

CNV-11965 for defect 1959287

SME/QE review

edit

sme review

sme review edit

peer review

edit for bullet
This commit is contained in:
Lavanya
2021-07-02 13:27:31 -04:00
committed by openshift-cherrypick-robot
parent f53ec84246
commit b2d95e8f69
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -41,6 +41,12 @@ Without an external monitoring system or a qualified human monitoring node healt
* If your cluster uses worker nodes from multiple CPU vendors, live migration failures can occur. For example, a virtual machine with an AMD CPU might attempt to live-migrate to a node with an Intel CPU and likely fail migration. To avoid this, label nodes with a vendor-specific label, such as `Vendor=Intel` or `Vendor=AMD`, and set node affinity on your virtual machines to ensure successful migration. 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 more information.
* All CPUs must be supported by Red Hat Enterprise Linux 8 and meet the following requirements:
** Intel 64 or AMD64 CPU extensions are supported
** Intel VT or AMD-V hardware virtualization extensions are enabled
** The no-execute (NX) flag is enabled
{VirtProductName} works with {product-title} by default, but the following installation configurations are recommended:
* Configure xref:../../monitoring/understanding-the-monitoring-stack.adoc#understanding-the-monitoring-stack[monitoring] in the cluster.