From cdab8d0586ff90ddc36150b4c53d8b010d66a0e1 Mon Sep 17 00:00:00 2001 From: Bob Gaydos Date: Wed, 10 Mar 2021 16:55:01 -0500 Subject: [PATCH] CNV-10445 [1926199] VM Migration to mixed CPU pool (AMD,Intel) --- virt/install/preparing-cluster-for-virt.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/virt/install/preparing-cluster-for-virt.adoc b/virt/install/preparing-cluster-for-virt.adoc index dea85a7ac3..4bcd8e7768 100644 --- a/virt/install/preparing-cluster-for-virt.adoc +++ b/virt/install/preparing-cluster-for-virt.adoc @@ -37,6 +37,8 @@ Without an external monitoring system or a qualified human monitoring node healt * To use proxy with {VirtProductName}, you must xref:../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[configure proxy support in Operator Lifecycle Manager]. +* 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. + {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.