diff --git a/docs/install/requirements.md b/docs/install/requirements.md
index 40e4f132e4e..d0cddb4a0fe 100644
--- a/docs/install/requirements.md
+++ b/docs/install/requirements.md
@@ -26,6 +26,7 @@ A three-node cluster is required to realize the multi-node features of Harvester
 - The first node always defaults to be a management node of the cluster.
 - When there are three or more nodes, the two other nodes added first are automatically promoted to management nodes to form a high availability (HA) cluster.
 - We recommend server-class hardware for the best results. Laptops and nested virtualization are not officially supported.
+- The `product_uuid` fetched from `/sys/class/dmi/id/product_uuid` in Linux must be unique in each node. Otherwise, features like VM live migration will be affected. For more information, refer to [#4025](https://github.com/harvester/harvester/issues/4025).
 :::
 
 ## Network requirements
@@ -80,4 +81,5 @@ When provisioning VMs with Kubernetes clusters from Rancher into Harvester, you
 For the port requirements for guest clusters deployed inside Harvester VMs, refer to the following links:
 - [K3s Networking](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#networking)
 - [RKE Ports](https://rancher.com/docs/rke/latest/en/os/#ports)
-- [RKE2 Networking](https://docs.rke2.io/install/requirements#networking)
\ No newline at end of file
+- [RKE2 Networking](https://docs.rke2.io/install/requirements#networking)
+
diff --git a/versioned_docs/version-v1.1/install/requirements.md b/versioned_docs/version-v1.1/install/requirements.md
index 40e4f132e4e..819a0466ef4 100644
--- a/versioned_docs/version-v1.1/install/requirements.md
+++ b/versioned_docs/version-v1.1/install/requirements.md
@@ -26,6 +26,7 @@ A three-node cluster is required to realize the multi-node features of Harvester
 - The first node always defaults to be a management node of the cluster.
 - When there are three or more nodes, the two other nodes added first are automatically promoted to management nodes to form a high availability (HA) cluster.
 - We recommend server-class hardware for the best results. Laptops and nested virtualization are not officially supported.
+- The `product_uuid` fetched from `/sys/class/dmi/id/product_uuid` in Linux must be unique in each node. Otherwise, features like VM live migration will be affected. For more information, refer to [#4025](https://github.com/harvester/harvester/issues/4025).
 :::
 
 ## Network requirements
@@ -80,4 +81,4 @@ When provisioning VMs with Kubernetes clusters from Rancher into Harvester, you
 For the port requirements for guest clusters deployed inside Harvester VMs, refer to the following links:
 - [K3s Networking](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#networking)
 - [RKE Ports](https://rancher.com/docs/rke/latest/en/os/#ports)
-- [RKE2 Networking](https://docs.rke2.io/install/requirements#networking)
\ No newline at end of file
+- [RKE2 Networking](https://docs.rke2.io/install/requirements#networking)