When creating a VirtualMachine with memory defined under resources.requests and memory.limits, the global memoryOvercommit setting is still applied.


# Overcommit in hco:
  "memoryOvercommitPercentage": 150


# Memory request/limits in VM spec:
        resources:
          limits:
            memory: 1Gi
          requests:
            memory: 1Gi

# Memory request/limits in virt-launcher pod:
    resources:
      limits:
        memory: 1294Mi
      requests:
        memory: "998943402"

4.20

100%

1. set "memoryOvercommitPercentage" greater than 100
2. create VM with memory.request in the spec instead of memory guest
3. 

virt-launcher pod calculates the request memory based on overcommit ratio setting

Overcommit ratio should only affect VMs with memory.guest

When memory.limits is used and memoryOvercommitPercentage < 100 is applied, the pod fails to start with error:


spec.containers[0].resources.requests: Invalid value: "2418Mi":
        must be less than or equal to memory limit of 1394Mi'