You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by cr...@istream.today on 2021/09/17 11:46:49 UTC
The RAM MEM inside KVM instance is not the same as it was set
Hello,
From where do I get this minRam value? I used a compute offering
with 10GB of RAM, if I check the VM I see 4GB Ram.
"[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","maxSpeed":"19
00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
10737418240","arch":"x86_64","os":"CentOS 7","platformEmulator":"CentOS
7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableDynamically
ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.100.22
.10""
Regards,
Cristian
RE: The RAM MEM inside KVM instance is not the same as it was set
Posted by cr...@istream.today.
HI Wei,
Thank you for the info.
Is there a way to do overprovisioning like we do with VMware? If I have an over provisioning of 1.5x or 2x, is there a way not to show the min value inside the instance, and show the max?
Regards,
Cristian
-----Original Message-----
From: Wei ZHOU <us...@gmail.com>
Sent: Wednesday, September 22, 2021 1:33 PM
To: users <us...@cloudstack.apache.org>
Subject: Re: The RAM MEM inside KVM instance is not the same as it was set
Hi Cristian,
4.15 branch only accepts bug fixes. I think it is not a bug but an enhancement.
-Wei
On Wed, 22 Sept 2021 at 12:19, <cr...@istream.today> wrote:
> Hi,
>
> is there a way to apply this to 4.15.2 ?
> https://github.com/apache/cloudstack/commit/6531ee587198ca2789ab0f53e9
> f3c3dccdd009d4
>
>
>
> Regards,
> Cristian
>
> -----Original Message-----
> From: Daniel Augusto Veronezi Salvador <gu...@apache.org>
> Sent: Friday, September 17, 2021 7:55 PM
> To: users@cloudstack.apache.org
> Subject: Re: The RAM MEM inside KVM instance is not the same as it was
> set
>
> Hi, Cristian,
>
> When ACS is deploying a VM, it defines a minimum memory|CPU to the VM,
> based on a calculation through the overprovisioning (defined mem|cpu
> speed / overprovisioning factor); Therefore, it will define a range of
> memory|CPU, even if it does not use scalable (dynamic) service offerings.
>
> For now, the option to avoid this behavior is to keep memory
> overprovisioning as "1", as Wei suggested. However, in version 4.16.0,
> there'll be two new global settings
> ("vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor"
> and
> "vm.min.cpu.speed.equals.cpu.speed.divided.by.cpu.overprovisioning.fac
> tor")
> to avoid it.
>
> This is the PR which introduced it:
> https://github.com/apache/cloudstack/pull/4722
>
> Best regards,
> Daniel
>
> On 2021/09/17 15:07:55, Wei ZHOU <us...@gmail.com> wrote:
> > For kvm environments, I suggest to set the value to 1 (in global
> > setting and cluster setting).
> >
> > -Wei
> >
> >
> > On Fri, 17 Sept 2021 at 16:19, <cr...@istream.today> wrote:
> >
> > > Hi,
> > >
> > > Yes, I have found that this is why i have this value.
> > >
> > >
> > > Regards,
> > > Cristian
> > >
> > > -----Original Message-----
> > > From: Wei ZHOU <us...@gmail.com>
> > > Sent: Friday, September 17, 2021 3:34 PM
> > > To: users <us...@cloudstack.apache.org>
> > > Subject: Re: The RAM MEM inside KVM instance is not the same as it
> > > was set
> > >
> > > Hi,
> > >
> > > Did you set mem.overprovisioning.factor in global setting or
> > > cluster setting ?
> > >
> > > -Wei
> > >
> > > On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
> > >
> > > > Hello,
> > > >
> > > >
> > > >
> > > > From where do I get this minRam value? I used a compute
> offering
> > > > with 10GB of RAM, if I check the VM I see 4GB Ram.
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
> > > >
> > > > ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","m
> > > > ax
> > > > Spee
> > > > d":"19
> > > > 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> > > > 10737418240","arch":"x86_64","os":"CentOS
> > > > 7","platformEmulator":"CentOS
> > > >
> > > > 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enabl
> > > > eD
> > > > ynam
> > > > ically
> > > >
> > > >
> ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.
> > > > 100.22
> > > > .10""
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Cristian
> > > >
> > > >
> > >
> > >
> >
>
>
Re: The RAM MEM inside KVM instance is not the same as it was set
Posted by Wei ZHOU <us...@gmail.com>.
Hi Cristian,
4.15 branch only accepts bug fixes. I think it is not a bug but an
enhancement.
-Wei
On Wed, 22 Sept 2021 at 12:19, <cr...@istream.today> wrote:
> Hi,
>
> is there a way to apply this to 4.15.2 ?
> https://github.com/apache/cloudstack/commit/6531ee587198ca2789ab0f53e9f3c3dccdd009d4
>
>
>
> Regards,
> Cristian
>
> -----Original Message-----
> From: Daniel Augusto Veronezi Salvador <gu...@apache.org>
> Sent: Friday, September 17, 2021 7:55 PM
> To: users@cloudstack.apache.org
> Subject: Re: The RAM MEM inside KVM instance is not the same as it was set
>
> Hi, Cristian,
>
> When ACS is deploying a VM, it defines a minimum memory|CPU to the VM,
> based on a calculation through the overprovisioning (defined mem|cpu speed
> / overprovisioning factor); Therefore, it will define a range of
> memory|CPU, even if it does not use scalable (dynamic) service offerings.
>
> For now, the option to avoid this behavior is to keep memory
> overprovisioning as "1", as Wei suggested. However, in version 4.16.0,
> there'll be two new global settings
> ("vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor" and
> "vm.min.cpu.speed.equals.cpu.speed.divided.by.cpu.overprovisioning.factor")
> to avoid it.
>
> This is the PR which introduced it:
> https://github.com/apache/cloudstack/pull/4722
>
> Best regards,
> Daniel
>
> On 2021/09/17 15:07:55, Wei ZHOU <us...@gmail.com> wrote:
> > For kvm environments, I suggest to set the value to 1 (in global
> > setting and cluster setting).
> >
> > -Wei
> >
> >
> > On Fri, 17 Sept 2021 at 16:19, <cr...@istream.today> wrote:
> >
> > > Hi,
> > >
> > > Yes, I have found that this is why i have this value.
> > >
> > >
> > > Regards,
> > > Cristian
> > >
> > > -----Original Message-----
> > > From: Wei ZHOU <us...@gmail.com>
> > > Sent: Friday, September 17, 2021 3:34 PM
> > > To: users <us...@cloudstack.apache.org>
> > > Subject: Re: The RAM MEM inside KVM instance is not the same as it
> > > was set
> > >
> > > Hi,
> > >
> > > Did you set mem.overprovisioning.factor in global setting or cluster
> > > setting ?
> > >
> > > -Wei
> > >
> > > On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
> > >
> > > > Hello,
> > > >
> > > >
> > > >
> > > > From where do I get this minRam value? I used a compute
> offering
> > > > with 10GB of RAM, if I check the VM I see 4GB Ram.
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
> > > >
> > > > ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","max
> > > > Spee
> > > > d":"19
> > > > 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> > > > 10737418240","arch":"x86_64","os":"CentOS
> > > > 7","platformEmulator":"CentOS
> > > >
> > > > 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableD
> > > > ynam
> > > > ically
> > > >
> > > >
> ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.
> > > > 100.22
> > > > .10""
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Cristian
> > > >
> > > >
> > >
> > >
> >
>
>
RE: The RAM MEM inside KVM instance is not the same as it was set
Posted by cr...@istream.today.
Hi,
is there a way to apply this to 4.15.2 ?https://github.com/apache/cloudstack/commit/6531ee587198ca2789ab0f53e9f3c3dccdd009d4
Regards,
Cristian
-----Original Message-----
From: Daniel Augusto Veronezi Salvador <gu...@apache.org>
Sent: Friday, September 17, 2021 7:55 PM
To: users@cloudstack.apache.org
Subject: Re: The RAM MEM inside KVM instance is not the same as it was set
Hi, Cristian,
When ACS is deploying a VM, it defines a minimum memory|CPU to the VM, based on a calculation through the overprovisioning (defined mem|cpu speed / overprovisioning factor); Therefore, it will define a range of memory|CPU, even if it does not use scalable (dynamic) service offerings.
For now, the option to avoid this behavior is to keep memory overprovisioning as "1", as Wei suggested. However, in version 4.16.0, there'll be two new global settings ("vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor" and "vm.min.cpu.speed.equals.cpu.speed.divided.by.cpu.overprovisioning.factor") to avoid it.
This is the PR which introduced it: https://github.com/apache/cloudstack/pull/4722
Best regards,
Daniel
On 2021/09/17 15:07:55, Wei ZHOU <us...@gmail.com> wrote:
> For kvm environments, I suggest to set the value to 1 (in global
> setting and cluster setting).
>
> -Wei
>
>
> On Fri, 17 Sept 2021 at 16:19, <cr...@istream.today> wrote:
>
> > Hi,
> >
> > Yes, I have found that this is why i have this value.
> >
> >
> > Regards,
> > Cristian
> >
> > -----Original Message-----
> > From: Wei ZHOU <us...@gmail.com>
> > Sent: Friday, September 17, 2021 3:34 PM
> > To: users <us...@cloudstack.apache.org>
> > Subject: Re: The RAM MEM inside KVM instance is not the same as it
> > was set
> >
> > Hi,
> >
> > Did you set mem.overprovisioning.factor in global setting or cluster
> > setting ?
> >
> > -Wei
> >
> > On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
> >
> > > Hello,
> > >
> > >
> > >
> > > From where do I get this minRam value? I used a compute offering
> > > with 10GB of RAM, if I check the VM I see 4GB Ram.
> > >
> > >
> > >
> > >
> > >
> > "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
> > >
> > > ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","max
> > > Spee
> > > d":"19
> > > 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> > > 10737418240","arch":"x86_64","os":"CentOS
> > > 7","platformEmulator":"CentOS
> > >
> > > 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableD
> > > ynam
> > > ically
> > >
> > > ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.
> > > 100.22
> > > .10""
> > >
> > >
> > >
> > >
> > >
> > > Regards,
> > >
> > > Cristian
> > >
> > >
> >
> >
>
Re: The RAM MEM inside KVM instance is not the same as it was set
Posted by Daniel Augusto Veronezi Salvador <gu...@apache.org>.
Hi, Cristian,
When ACS is deploying a VM, it defines a minimum memory|CPU to the VM, based on a calculation through the overprovisioning (defined mem|cpu speed / overprovisioning factor); Therefore, it will define a range of memory|CPU, even if it does not use scalable (dynamic) service offerings.
For now, the option to avoid this behavior is to keep memory overprovisioning as "1", as Wei suggested. However, in version 4.16.0, there'll be two new global settings ("vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor" and "vm.min.cpu.speed.equals.cpu.speed.divided.by.cpu.overprovisioning.factor") to avoid it.
This is the PR which introduced it: https://github.com/apache/cloudstack/pull/4722
Best regards,
Daniel
On 2021/09/17 15:07:55, Wei ZHOU <us...@gmail.com> wrote:
> For kvm environments, I suggest to set the value to 1 (in global setting
> and cluster setting).
>
> -Wei
>
>
> On Fri, 17 Sept 2021 at 16:19, <cr...@istream.today> wrote:
>
> > Hi,
> >
> > Yes, I have found that this is why i have this value.
> >
> >
> > Regards,
> > Cristian
> >
> > -----Original Message-----
> > From: Wei ZHOU <us...@gmail.com>
> > Sent: Friday, September 17, 2021 3:34 PM
> > To: users <us...@cloudstack.apache.org>
> > Subject: Re: The RAM MEM inside KVM instance is not the same as it was set
> >
> > Hi,
> >
> > Did you set mem.overprovisioning.factor in global setting or cluster
> > setting ?
> >
> > -Wei
> >
> > On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
> >
> > > Hello,
> > >
> > >
> > >
> > > From where do I get this minRam value? I used a compute offering
> > > with 10GB of RAM, if I check the VM I see 4GB Ram.
> > >
> > >
> > >
> > >
> > >
> > "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
> > >
> > > ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","maxSpee
> > > d":"19
> > > 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> > > 10737418240","arch":"x86_64","os":"CentOS
> > > 7","platformEmulator":"CentOS
> > >
> > > 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableDynam
> > > ically
> > >
> > > ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.
> > > 100.22
> > > .10""
> > >
> > >
> > >
> > >
> > >
> > > Regards,
> > >
> > > Cristian
> > >
> > >
> >
> >
>
Re: The RAM MEM inside KVM instance is not the same as it was set
Posted by Wei ZHOU <us...@gmail.com>.
For kvm environments, I suggest to set the value to 1 (in global setting
and cluster setting).
-Wei
On Fri, 17 Sept 2021 at 16:19, <cr...@istream.today> wrote:
> Hi,
>
> Yes, I have found that this is why i have this value.
>
>
> Regards,
> Cristian
>
> -----Original Message-----
> From: Wei ZHOU <us...@gmail.com>
> Sent: Friday, September 17, 2021 3:34 PM
> To: users <us...@cloudstack.apache.org>
> Subject: Re: The RAM MEM inside KVM instance is not the same as it was set
>
> Hi,
>
> Did you set mem.overprovisioning.factor in global setting or cluster
> setting ?
>
> -Wei
>
> On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
>
> > Hello,
> >
> >
> >
> > From where do I get this minRam value? I used a compute offering
> > with 10GB of RAM, if I check the VM I see 4GB Ram.
> >
> >
> >
> >
> >
> "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
> >
> > ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","maxSpee
> > d":"19
> > 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> > 10737418240","arch":"x86_64","os":"CentOS
> > 7","platformEmulator":"CentOS
> >
> > 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableDynam
> > ically
> >
> > ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.
> > 100.22
> > .10""
> >
> >
> >
> >
> >
> > Regards,
> >
> > Cristian
> >
> >
>
>
RE: The RAM MEM inside KVM instance is not the same as it was set
Posted by cr...@istream.today.
Hi,
Yes, I have found that this is why i have this value.
Regards,
Cristian
-----Original Message-----
From: Wei ZHOU <us...@gmail.com>
Sent: Friday, September 17, 2021 3:34 PM
To: users <us...@cloudstack.apache.org>
Subject: Re: The RAM MEM inside KVM instance is not the same as it was set
Hi,
Did you set mem.overprovisioning.factor in global setting or cluster setting ?
-Wei
On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
> Hello,
>
>
>
> From where do I get this minRam value? I used a compute offering
> with 10GB of RAM, if I check the VM I see 4GB Ram.
>
>
>
>
> "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
>
> ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","maxSpee
> d":"19
> 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> 10737418240","arch":"x86_64","os":"CentOS
> 7","platformEmulator":"CentOS
>
> 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableDynam
> ically
>
> ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.
> 100.22
> .10""
>
>
>
>
>
> Regards,
>
> Cristian
>
>
Re: The RAM MEM inside KVM instance is not the same as it was set
Posted by Wei ZHOU <us...@gmail.com>.
Hi,
Did you set mem.overprovisioning.factor in global setting or cluster
setting ?
-Wei
On Fri, 17 Sept 2021 at 13:47, <cr...@istream.today> wrote:
> Hello,
>
>
>
> From where do I get this minRam value? I used a compute offering
> with 10GB of RAM, if I check the VM I see 4GB Ram.
>
>
>
>
> "[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"4156","name":"i-2-4156-VM"
>
> ,"state":"Starting","type":"User","cpus":"4","minSpeed":"760","maxSpeed":"19
> 00","minRam":"(4.00 GB) 4294967296","maxRam":"(10.00 GB)
> 10737418240","arch":"x86_64","os":"CentOS 7","platformEmulator":"CentOS
>
> 7","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableDynamically
>
> ScaleVm":"false","vncPassword":"NutaRZIRWThdE3aU_IkJAA","vncAddr":"10.100.22
> .10""
>
>
>
>
>
> Regards,
>
> Cristian
>
>