Looks like it works as of 4.2, but you need to update existing cluster settings, rather than global (or both, I suppose).
On Fri, Jan 24, 2014 at 3:17 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > I guess not. It should work though. We ran into the same issue with > storage, everything hardcoded to only work with vmware. I'll take a > look. > > On Mon, Oct 7, 2013 at 1:09 PM, Sebastien Goasguen <run...@gmail.com> wrote: >> >> On Sep 25, 2013, at 2:59 AM, Harikrishna Patnala >> <harikrishna.patn...@citrix.com> 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 <niki...@yahoo.com> wrote: >>> >>>> Yes Kirk, I did >>>> >>>> >>>> >>>> ________________________________ >>>> From: Kirk Jantzer <kirk.jant...@gmail.com> >>>> To: Cloudstack users mailing list <users@cloudstack.apache.org>; Nikolay >>>> Kabadjov <niki...@yahoo.com> >>>> 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 <niki...@yahoo.com> >>>> 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 >>> >>
