https://rancher.com/ logo
Title
c

crooked-scooter-58172

12/07/2022, 7:47 PM
Team, It seems that Harvester doesn’t consider “_*requests.memory*_” param while assigning memory for a VM. It always use the limit memory (minus some overhead) and assign that much of memory to the VM. I am just wondering whether others faced the similar issue. If yes, then any suggestions?
f

full-plastic-79795

12/08/2022, 4:16 AM
Harvester vm's requests.memory will be calculated automatically according to https://docs.harvesterhci.io/v1.1/vm/resource-overcommit and the limit memory.
c

crooked-scooter-58172

12/08/2022, 6:39 PM
Thanks @full-plastic-79795. Is there anyway we can disable global overcommit?
The document is saying that we can configure overcommit for single VM "_If you need to configure individual virtual machines without involving global configuration, consider adjusting the
spec.template.spec.domain.resources.<memory|cpu>
value on the target VirtualMachine resource individually. Note that by modifying these values, you are taking over control of virtual machine resource management from Harvester._"
However when I set the request values it doesn't use them