From 97ce22bd5507f8a305d62dce20d2a44633aa3028 Mon Sep 17 00:00:00 2001 From: Ashleigh Brennan Date: Tue, 25 Nov 2025 11:47:29 -0600 Subject: [PATCH] CNV-65188: Update resource limit minimum values --- ...setting-resource-quota-limits-for-vms.adoc | 20 ++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/modules/virt-setting-resource-quota-limits-for-vms.adoc b/modules/virt-setting-resource-quota-limits-for-vms.adoc index 2f1d871ddd..5f78a69749 100644 --- a/modules/virt-setting-resource-quota-limits-for-vms.adoc +++ b/modules/virt-setting-resource-quota-limits-for-vms.adoc @@ -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.