Hi Hari, This is the same as earlier . We use to set the reserved memory and the memory (i call this max ) in case of vmware (we had the support for memory overcommit in vmware, it was not per cluster basis.).
reserved memory = memory in the offering/overcommit ratio. memory(max memory)= memory in the service offering. Bharat. On Feb 21, 2013, at 1:02 AM, Hari Kannan <hari.kan...@citrix.com> wrote: > Hi Bharat, > > Sorry, I still don't understand - are you referring to the dynamic memory > scale-up feature on XS? I'm not aware of VMware requiring the setting of > min/max ranges for memory for a VM because of overcommit - can you please > detail what the setting before this change was and what you intend to do > because of this feature? > > Hari > > -----Original Message----- > From: Bharat Kumar [mailto:bharat.ku...@citrix.com] > Sent: Wednesday, February 20, 2013 4:18 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: Regarding cpu and ram overcommit feature > > Hi Hari, > > When we change the overcommit ratio the newly deployed VMs will be deployed > with the new settings for the memory and cpu while the VMs prior to the > change will use the same settings. > We are using memory ballooning which requires setting of the min and max > ranges for memory on a per VM basis. > > > On Feb 19, 2013, at 9:49 PM, Hari Kannan <hari.kan...@citrix.com> wrote: > >> Hi Bharat, >> >> Can you please respond on the mailing list? >> >> Hari >> >> -----Original Message----- >> From: Hari Kannan >> Sent: Thursday, February 14, 2013 9:19 AM >> To: cloudstack-dev@incubator.apache.org >> Subject: RE: Regarding cpu and ram overcommit feature >> >> Hi Bharat, >> >> Can you please shed some more light on this? Why does changing the >> overcommit have any impact on VMs? Is it hypervisor platform specific? Can >> you please provide an example of before and after? >> >> Hari >> >> -----Original Message----- >> From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] >> Sent: Wednesday, February 13, 2013 3:05 AM >> To: cloudstack-dev@incubator.apache.org >> Subject: Re: Regarding cpu and ram overcommit feature >> >> As part of the current implementation changing the overcommit ratio will not >> have immediate affect on the VM already running. >> >> -abhi >> >> On 13/02/13 4:19 PM, "Bharat Kumar" <bharat.ku...@citrix.com> wrote: >> >>> Hi All, >>> >>> After some discussion i think the new overcommit ratio should not >>> affect the VMs already deployed. It will only effect the VMs deployed >>> after the change. >>> I we need to reconfigure the previously running VMs we need to stop >>> start them. I will call this out in the Functional spec. >>> >>> Bharat. >>> >>> >> >
