diff --git a/virt/install/preparing-cluster-for-virt.adoc b/virt/install/preparing-cluster-for-virt.adoc
index 3478f0c894..72087b7a6b 100644
--- a/virt/install/preparing-cluster-for-virt.adoc
+++ b/virt/install/preparing-cluster-for-virt.adoc
@@ -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.