There's no support for memory overprovisioning in CS 4.1.1 and earlier. That global parameter causes a lot of confusion since despite the name it does not enable memory overprovisioning. Memory overprivisioning support has been added to CS 4.2, but it uses cluster-level settings and not the global parameter. This is explained in the admin guide, and the design details are here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CPU+and+RAM+Overcommit Best regards, Kirk has been added in 4.2, but read the documentation On 10/07/2013 12:09 PM, Sebastien Goasguen wrote: > > On Sep 25, 2013, at 2:59 AM, Harikrishna Patnala > <[email protected]> wrote: > >> As far as I know men over provisioning is intended to work only with VMWare >> hypervisor to allocate reserved memory for VM. >> > > @Marcus, could you comment on this: is mem over provisioning supposed to work > with KVM ? > >> On 25-Sep-2013, at 11:11 AM, Nikolay Kabadjov <[email protected]> wrote: >> >>> Yes Kirk, I did >>> >>> >>> >>> ________________________________ >>> From: Kirk Jantzer <[email protected]> >>> To: Cloudstack users mailing list <[email protected]>; Nikolay >>> Kabadjov <[email protected]> >>> Sent: Tuesday, September 24, 2013 5:50 PM >>> Subject: Re: mem.overprovisioning.facto and KVM >>> >>> >>> >>> Did you restart the management service after making the change? >>> >>> >>> >>> Regards, >>> >>> Kirk Jantzer >>> http://about.me/kirkjantzer >>> >>> >>> >>> On Tue, Sep 24, 2013 at 10:25 AM, Nikolay Kabadjov <[email protected]> >>> wrote: >>> >>> Hi all, >>>> I've noticed that increasing mem.overprovisioning.factor doesn't take >>>> effect? >>>> I mean I still see in the dashboard the exact amount of memory I have >>>> multiplying the memory of all the hosts. >>>> >>>> It's CS 4.1.1 with one zone, one pod, one cluster, 6 KVM hosts >>>> >>>> Any idea? >>>> >>>> Thanks >>>> Niki >> >
