Skip to content

Commit

Permalink
emphasis Product_UUID needs to be unique
Browse files Browse the repository at this point in the history
Signed-off-by: Jian Wang <w13915984028@gmail.com>
  • Loading branch information
w13915984028 authored and guangbochen committed Jun 29, 2023
1 parent 6352fd7 commit e09f701
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
4 changes: 3 additions & 1 deletion docs/install/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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)
- [RKE2 Networking](https://docs.rke2.io/install/requirements#networking)

3 changes: 2 additions & 1 deletion versioned_docs/version-v1.1/install/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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)
- [RKE2 Networking](https://docs.rke2.io/install/requirements#networking)

0 comments on commit e09f701

Please sign in to comment.