Hi Niclose, I think the issue is the all the vm that created before the factor created need to power off and power on back, then only it will take effect.
However overprovisioning Memory is not a good way to implement too . For example if the Overprovisioning factor for Memory set to 3, and install a VM that 1G ram, the actual ram that the VM get is around 400M , it can see at free -m inside LInux for memory inside VM. On Tue, Feb 2, 2021 at 12:43 PM Nicolas Vazquez < nicolas.vazq...@shapeblue.com> wrote: > Hi Hean, > > Can you describe your environment and provide an example of the issue you > are facing as the example in this section of the docs? > http://docs.cloudstack.apache.org/en/latest/adminguide/hosts.html#over-provisioning-and-service-offering-limits > > > Regards, > > Nicolas Vazquez > > ________________________________ > From: Hean Seng <heans...@gmail.com> > Sent: Wednesday, January 27, 2021 5:12 AM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: Cluster Memory Overprovisioning > > Hi > > Anybody have experience if memory over provisioning is working ? > > I set the over provisioning factor to higher in the cluster. > However the hypervisor host Memory allocated follows increasing and is > not able to over provision. Each VM, have only 1G and 2G RAM . > > > [image.png] > > > -- > Regards, > Hean Seng > > nicolas.vazq...@shapeblue.com > www.shapeblue.com > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK > @shapeblue > > > > -- Regards, Hean Seng
