Skip to content

Add reference that some CPU is reserved for system #860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 1, 2025
+20 −0
Merged

Add reference that some CPU is reserved for system #860

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f530ae5
Add reference that some CPU is reserved for system
martindekov Aug 27, 2025
71afa2e
Add further context on why cores might show less
martindekov Aug 27, 2025
d9f46e6
Add info section to version 1.6 as well
martindekov Sep 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/host/host.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ Because Harvester is built on top of Kubernetes and uses etcd as its database, t

![host.png](/img/v1.2/host/host.png)

:::info

Harvester reserves CPU resources for system-level operations on each node. For more information, see [Calculation of Shared CPU Pool](../vm/cpu-pinning.md#calculation-of-shared-cpu-pool). This is why the total cores shown on the CPU column is slightly less than the real CPU cores on each node.

:::
## Node Maintenance

Admin users can enable Maintenance Mode (select **⋮ > Enable Maintenance Mode**) to automatically evict all virtual machines from a node. This mode leverages [batch migration](../vm/live-migration.md#automatically-triggered-batch-migration) to move the [live-migratable virtual machines](../vm/live-migration.md#live-migratable-virtual-machines) to other nodes, which is useful when you need to reboot, upgrade firmware, or replace hardware components. At least two active nodes are required to use this feature.
Expand Down
5 changes: 5 additions & 0 deletions versioned_docs/version-v1.4/host/host.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ Because Harvester is built on top of Kubernetes and uses etcd as its database, t

![host.png](/img/v1.2/host/host.png)

:::info

Harvester reserves CPU resources for system-level operations on each node. For more information, see [Calculation of Shared CPU Pool](../vm/cpu-pinning.md#calculation-of-shared-cpu-pool). This is why the total cores shown on the CPU column is slightly less than the real CPU cores on each node.

:::
## Node Maintenance

Admin users can enable Maintenance Mode (select **⋮ > Enable Maintenance Mode**) to automatically evict all virtual machines from a node. This mode leverages the **live migration** feature to migrate the virtual machines to other nodes, which is useful when you need to reboot, upgrade firmware, or replace hardware components. At least two active nodes are required to use this feature.
Expand Down
5 changes: 5 additions & 0 deletions versioned_docs/version-v1.5/host/host.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ Because Harvester is built on top of Kubernetes and uses etcd as its database, t

![host.png](/img/v1.2/host/host.png)

:::info

Harvester reserves CPU resources for system-level operations on each node. For more information, see [Calculation of Shared CPU Pool](../vm/cpu-pinning.md#calculation-of-shared-cpu-pool). This is why the total cores shown on the CPU column is slightly less than the real CPU cores on each node.

:::
## Node Maintenance

Admin users can enable Maintenance Mode (select **⋮ > Enable Maintenance Mode**) to automatically evict all virtual machines from a node. This mode leverages the **live migration** feature to migrate the virtual machines to other nodes, which is useful when you need to reboot, upgrade firmware, or replace hardware components. At least two active nodes are required to use this feature.
Expand Down
5 changes: 5 additions & 0 deletions versioned_docs/version-v1.6/host/host.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ Because Harvester is built on top of Kubernetes and uses etcd as its database, t

![host.png](/img/v1.2/host/host.png)

:::info

Harvester reserves CPU resources for system-level operations on each node. For more information, see [Calculation of Shared CPU Pool](../vm/cpu-pinning.md#calculation-of-shared-cpu-pool). This is why the total cores shown on the CPU column is slightly less than the real CPU cores on each node.

:::
## Node Maintenance

Admin users can enable Maintenance Mode (select **⋮ > Enable Maintenance Mode**) to automatically evict all virtual machines from a node. This mode leverages [batch migration](../vm/live-migration.md#automatically-triggered-batch-migration) to move the [live-migratable virtual machines](../vm/live-migration.md#live-migratable-virtual-machines) to other nodes, which is useful when you need to reboot, upgrade firmware, or replace hardware components. At least two active nodes are required to use this feature.
Expand Down