cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: Regarding cpu and ram overcommit feature
Date Thu, 14 Feb 2013 19:14:27 GMT
On Thu, Feb 14, 2013 at 09:19:16AM -0800, Hari Kannan wrote:
> 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?

This confuses me as well.

> 
> Hari
> 
> -----Original Message-----
> From: Abhinandan Prateek [mailto:Abhinandan.Prateek@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.kumar@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.
> >
> > 
> 
> 

Mime
View raw message