[DOC] It is possible to assign > 254 vCPU to a VM #972
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
requested review from
akashraj4261,
dariavladykina and
jillian-maroket
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Harvester documentation to reflect that version 1.7 now supports allocating more than 254 vCPUs to virtual machines, enabled by automatic IOMMU activation in the underlying libvirt version.
Changes:
- Updated CPU allocation documentation from "a maximum of 254 vCPUs" to "more than 254 vCPUs" for Harvester v1.7
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/vm/create-vm.md | Updated CPU allocation limit documentation for the main docs |
| versioned_docs/version-v1.7/vm/create-vm.md | Updated CPU allocation limit documentation for v1.7 versioned docs |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
votdev
force-pushed
the
issue_8118_vcpu
branch
from
e9431c0 to
2eef416
Compare
votdev
changed the title
votdev
force-pushed
the
issue_8118_vcpu
branch
from
2eef416 to
e4c49c4
Compare
Starting with Harvester v1.6, it is possible to allocate more than 254 vCPUs, as the underlying libvirt version supports automatic activation of IOMMU. Related to: harvester/harvester#8118 Signed-off-by: Volker Theile <[email protected]>
votdev
force-pushed
the
issue_8118_vcpu
branch
from
e4c49c4 to
ebb36e6
Compare
ihcsim
reviewed
Feb 5, 2026
| 1. (Optional) VM template is optional, you can choose `iso-image`, `raw-image` or `windows-iso-image` template to speed up your VM instance creation. | ||
| 1. On the **Basics** tab, configure the following settings: | ||
| - **CPU** and **Memory**: You can allocate a maximum of **254** vCPUs. If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation. As a best practice, the number of virtual CPUs (vCPUs) allocated per virtual machine should not exceed the physical processor threads available on the host. | ||
| - **CPU** and **Memory**: You can allocate vCPUs as needed. If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation. As a best practice, the number of virtual CPUs (vCPUs) allocated per virtual machine should not exceed the physical processor threads available on the host. |
Contributor
There was a problem hiding this comment.
Suggested change
| - **CPU** and **Memory**: You can allocate vCPUs as needed. If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation. As a best practice, the number of virtual CPUs (vCPUs) allocated per virtual machine should not exceed the physical processor threads available on the host. | |
| - **CPU** and **Memory**: If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation. As a best practice, the number of virtual CPUs (vCPUs) allocated per virtual machine should not exceed the physical processor threads available on the host. |
or just remove it entirely?
Member
Author
There was a problem hiding this comment.
Yes, makes sense. Let's see what @harvester/doc says.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with Harvester v1.6, it is possible to allocate more than 254 vCPUs, as the underlying libvirt version supports automatic activation of IOMMU.
Related Issue(s):
harvester/harvester#8118