GitHub user bhouse-nexthop added a comment to the discussion: Disable cluster.memory.allocated.capacity.disablethreshold check? Bad interaction with mem.overprovisioning.factor
I'm monitoring actual memory usage per hypervisor separately. These are for developer VMs so we know they spike and release. It is understood that any sort of overcommit could lead to significant issues if not properly monitored. It appears setting the `mem.overprovisioning.factor` only applies to VMs *created* newly. It doesn't appear there is any way to change this setting. Even stopping and starting VMs doesn't change it, we can see the overprovisioning factor set in the VM settings stay at whatever the original value was. I had to make a direct DB edit: ``` update vm_instance_details set value=4 where name='memoryOvercommitRatio'; ``` So I guess this is expected behavior, but doesn't appear to be obvious. Its not entirely clear why it works this way. GitHub link: https://github.com/apache/cloudstack/discussions/12301#discussioncomment-15298683 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
