Hi, I don't believe RAM over-provisioning is implemented yet. There has been some discussion about it [1] and a functional spec was written [2], but AFAIK that is all that has been completed so far.
The mem.overprovisioning.factor parameter doesn't do what it sounds like it does. IIRC it only modifies the amount of host RAM that CloudStack will use so you can run non-CloudStack VMs on the host. It won't actually let you run any extra VMs through CloudStack. Also, I think it only has an effect with vSphere clusters. Best regards, Kirk [1] http://markmail.org/message/u6i5mdwyf42icsff [2] https://cwiki.apache.org/CLOUDSTACK/cpu-and-ram-overcommit.html On 07/10/2013 08:13 PM, Tao Lin wrote: > Thanks for your reply, Salvatore. I do notice that there is a option > relates to over-commit.And I now want to know that if cloudstack will > automatic balloon memory amount VMs, so that a busy VM can borrow memory > from another VM which is mostly idle by ballooning memory? > > > Best regard. > > > 2013/7/8 Salvatore Sciacco <scia...@iperweb.com> > >> There is a global setting parameter afaik... >> Il giorno 08/lug/2013 11:45, "Tao Lin" <linba...@gmail.com> ha scritto: >> >>> Hi,there: >>> Does cloudstack support memory-overcommitting so that memory resource >>> can be scheduled among VMs using the balloon device of the KVM? And how >>> cloudstack handle this? >>> >>> >>> Best regards. >>> >> >
