openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Merge pull request #103880 from openshift-cherrypick-robot/cherry-pick-103045-to-enterprise-4.21

Browse Source 
[enterprise-4.21] CNV-65188: Update resource limit minimum values
This commit is contained in:
Ashleigh Brennan
2025-12-12 12:51:14 -06:00
committed by GitHub
parent 85606e6d27 97ce22bd55
commit f74bb09cef
1 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
modules/virt-setting-resource-quota-limits-for-vms.adoc
View File

@@ -21,8 +21,8 @@ $ oc label ns/my-virtualization-project alpha.kubevirt.io/auto-memory-limits-ra
Avoid managing resource quota limits manually. To prevent misconfigurations or scheduling issues, rely on the automatic resource limit management provided by {VirtProductName} unless you have a specific need to override the defaults.
====
Resource quotas that only use requests automatically work with VMs. If your resource quota uses limits, you must manually set resource limits on VMs. Resource limits must be at least 100 MiB larger than resource requests.
Resource quotas that only use requests automatically work with VMs. If your resource quota uses limits, you must manually set resource limits on VMs.
Memory resource limits, defined by the `spec.template.spec.domain.resources.limits.memory` value, must be at least 500 MiB, or 2% larger than the `spec.template.spec.domain.memory.guest` value.
.Procedure
@@ -39,13 +39,19 @@ spec:
template:
spec:
domain:
# ...
memory:
guest: 128Mi
resources:
requests:
memory: 128Mi
limits:
memory: 256Mi <1>
memory: 256Mi
----
<1> This configuration is supported because the `limits.memory` value is at least `100Mi` larger than the `requests.memory` value.
+
where
+
spec.template.spec.domain.memory.guest:: Specifies the actual amount of RAM that is shown to the guest operating system (OS) in the VM.
+
spec.template.spec.domain.resources.limits.memory:: Specifies the hard limit for total memory consumption by the `virt-launcher` pod that hosts the VM. This limit must account for the guest OS RAM plus the hypervisor overhead.
+
This example configuration is supported because the `spec.template.spec.domain.resources.limits.memory` value is at least `100Mi` larger than the `spec.template.spec.domain.memory.guest` value.
. Save the `VirtualMachine` manifest.