RE: The RAM MEM inside KVM instance is not the same as it was set
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
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 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, wrote:
>
> > Hi,
> >
> > Yes, I have found that this is why i have this value.
> >
> >
> > Regards,
> > Cristian
> >
> > -Original Message-
> > From: Wei ZHOU
> > Sent: Friday, September 17, 2021 3:34 PM
> > To: users
> > 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, 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
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, 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
> 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 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, wrote:
> >
> > > Hi,
> > >
> > > Yes, I have found that this is why i have this value.
> > >
> > >
> > > Regards,
> > > Cristian
> > >
> > > -Original Message-
> > > From: Wei ZHOU
> > > Sent: Friday, September 17, 2021 3:34 PM
> > > To: users
> > > 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, 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: ACS Baremetal
Hi Alex, Here's slide from a talk on baremetal few years ago: http://events17.linuxfoundation.org/sites/events/files/slides/Baremetal-v4.1a.pdf ... and an old design doc: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Baremetal Regards. From: Alex Mattioli Sent: Monday, September 20, 2021 22:20 To: users@cloudstack.apache.org Subject: ACS Baremetal Hi all, Do any of you (or anyone you know of) use Cloudstack to deploy bare metal? If so, what's the use case? Thanks, Alex
Re: Problem with Templates/ISO
Sure, I am happy to contribute! By the way, just some more clarifications on the issue: The gateway interface can stay with "Promiscuous Mode: Deny." Only the interface of the VM we use to deploy CloudStack should be "Promiscuous Mode: Allow All." (Also, "All VMs" setting works fine.) This makes sense because if the traffic from the system VMs can hit the gateway, they should be able to access the Internet. It is the interface of the cloudstack VM (VM2) that denies traffic from the system VMs when it is not promiscuous. On Wed, Sep 22, 2021 at 2:36 AM Wei ZHOU wrote: > Hi Douglas, > > Thanks for sharing. > > I recall there is a similar issue with a nested environment on vmware ( > https://github.com/apache/cloudstack/issues/5000). > It would be good to mention it in the cloudstack document. > > Could you please create a pull request for it ? > https://github.com/apache/cloudstack-documentation > > -Wei > > > > On Wed, 22 Sept 2021 at 03:11, DL wrote: > > > Dear Pearl, Harikrishna, and Wei, > > > > Thank you all for your helpful input! > > With great joy, I'd like to share the reason for the various issues I > > encountered when following the Quick Installation Guide. > > > > In short, the reason is that the network adapters of the VMs that I use > to > > deploy CloudStack are not in the correct Promiscuous Mode. After I set > the > > network adapters as "Promiscuous Mode: Allow All" in VirtualBox, all the > > issues are gone! > > > > As I mentioned before, I am using one VM as the gateway server, and one > VM > > to deploy CloudStack. Let's call the VM that serves as the gateway server > > as VM1, and the VM that I want to deploy CloudStack onto as VM2. > > VM1 has two interfaces. The first interface enp0s3 is a NAT adapter. So, > > this interface uses DHCP and gets Internet access automatically. The > second > > interface, enp0s8, with IP address 172.16.10.1 is an Internal Network > > adapter. It is the gateway. > > VM2 has only one interface, enp0s3, which is also an Internal Network > > adapter. It uses IP 172.16.10.2. > > VM2 can have Internet access through the gateway. However, according to > the > > Quick Installation Guide, other VMs created on this VM2 all attach to the > > newly created bridge (cloudbr0) first. > > Initially, I used the default setting for the Promiscuous Mode (i.e., > Deny) > > for adapters enp0s8 on VM1 and enp0s3 on VM2. It seems that, with this > > setting, the system VMs created by CloudStack cannot reach the gateway > > 172.16.10.1, and thus cannot connect to the Internet. As all symptoms > point > > to a connectivity issue, I tried several hypotheses to try to resolve > > the issue. > > After I changed the Promiscuous Mode to "Allow All" for the two adapters > in > > VirtualBox, now the system VMs can connect to the Internet fine! > > > > I have successfully created an ISO through URL and launched a VM with the > > ISO! > > I still could not upload an ISO from the local file system. As this is > > expected, I will not try to get this feature working. I will just create > > ISOs through URLs if I need any. > > > > > > Do you think configuring the network adapters as "Promiscuous Mode: Allow > > All" (or at least as Allow VMs) should be mentioned in the Quick > > Installation Guide? > > I believe many people are using the virtual environment to test drive > > CloudStack. > > I am not sure whether this is a basic setting that everyone will > > automatically use. But this setting is in the Advanced setting section in > > VirtualBox, and the default setting is "Deny" even for Internal Network > > adapters. > > If this can be mentioned in the installation guide beforehand, it can > > potentially save the time newcomers may need to spend to realize that > this > > is a problem. > > > > Thanks again for the help! > > > > Best regards, > > Douglas > > > > > > > > > > On Tue, Sep 21, 2021 at 6:54 PM DL wrote: > > > > > Hello Wei, > > > > > > Thanks for the comment. Yes, the problem seems to be here. If I go to > the > > > SSVM console, it cannot connect to the Internet. > > > The consoleproxy VM cannot connect to the Internet either. > > > > > > I don't think I should change configurations within these system VMs, > as > > > the Quick Installation Guide doesn't mention anything about configuring > > the > > > system VMs. > > > Is it because I missed something during the previous configuration > > > process? What could have caused this problem? > > > > > > Best regards, > > > > > > > > > On Tue, Sep 21, 2021 at 3:55 PM Wei ZHOU > wrote: > > > > > >> It looks ssvm is not working well. > > >> Please make sure that ssvm can connect to internet. > > >> > > >> -Wei > > >> > > >> On Tuesday, 21 September 2021, DL wrote: > > >> > > >> > The "SystemVM Template (KVM)" is ready. However, the "CentOS > > 5.5(64bit) > > >> no > > >> > GUI (KVM)" template is not ready; the status says "Unable to resolve > > >> > download.cloudstack.org." > > >> > This issue is similar to the error I enc
RE: The RAM MEM inside KVM instance is not the same as it was set
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
Sent: Wednesday, September 22, 2021 1:33 PM
To: users
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, 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
> 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 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, wrote:
> >
> > > Hi,
> > >
> > > Yes, I have found that this is why i have this value.
> > >
> > >
> > > Regards,
> > > Cristian
> > >
> > > -Original Message-
> > > From: Wei ZHOU
> > > Sent: Friday, September 17, 2021 3:34 PM
> > > To: users
> > > 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, 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: Adding OS Type
Hi Do you know what is addGuestOS Details (*Map of (key/value pairs))**. *refer to? This compulsory field, and do not know what it means . I am using KVM , the API doc did not explain on i t. On Mon, Sep 20, 2021 at 3:48 PM Hean Seng wrote: > How about is that possible to change the OSType for existing > Uploaed Template. > > Currently we upload Ubuntu 20 type Other Ubuntu , after added the New > OS, with to change to Proper OS Type > > On Mon, Sep 20, 2021 at 3:46 PM Hean Seng wrote: > >> Thanks for this info. Overlook on this API. >> >> On Mon, Sep 20, 2021 at 2:13 PM Daan Hoogland >> wrote: >> >>> yes, there are some APIs to aid with that: >>> http://cloudstack.apache.org/api/apidocs-4.15/apis/addGuestOs.html >>> http://cloudstack.apache.org/api/apidocs-4.15/apis/addGuestOsMapping.html >>> >>> On Mon, Sep 20, 2021 at 3:25 AM Hean Seng wrote: >>> >>> > Hi >>> > >>> > Is there any way to add OS Type in ACS template ? Currently using >>> 4.15 >>> > >>> > We need to add in as new OS is coming out , eg Debian 11, Ubuntu 20 >>> etc. >>> > >>> > >>> > -- >>> > Regards, >>> > Hean Seng >>> > >>> >>> >>> -- >>> Daan >>> >> >> >> -- >> Regards, >> Hean Seng >> > > > -- > Regards, > Hean Seng > -- Regards, Hean Seng
Re: Adding OS Type
Hi Hean, The details are not applicable for kvm. I do not know why it is required. you can use the same details as other guest os xenserver.dynamicMin = 536870912 xenserver.dynamicMax = 137438953472 I suggest you NOT add a new guest os if you use 4.15.0.0 or older versions, because the upgrade sql from 4.15.0.0 to 4.15.1.0 have hardcoded id for some guest os. no issue with 4.15.1.0 or 4.15.2.0. -Wei On Wed, 22 Sept 2021 at 22:09, Hean Seng wrote: > Hi > > Do you know what is addGuestOS Details (*Map of (key/value pairs))**. > *refer > to? > > This compulsory field, and do not know what it means . I am using KVM , > the API doc did not explain on i t. > > > > > > > > On Mon, Sep 20, 2021 at 3:48 PM Hean Seng wrote: > > > How about is that possible to change the OSType for existing > > Uploaed Template. > > > > Currently we upload Ubuntu 20 type Other Ubuntu , after added the New > > OS, with to change to Proper OS Type > > > > On Mon, Sep 20, 2021 at 3:46 PM Hean Seng wrote: > > > >> Thanks for this info. Overlook on this API. > >> > >> On Mon, Sep 20, 2021 at 2:13 PM Daan Hoogland > >> wrote: > >> > >>> yes, there are some APIs to aid with that: > >>> http://cloudstack.apache.org/api/apidocs-4.15/apis/addGuestOs.html > >>> > http://cloudstack.apache.org/api/apidocs-4.15/apis/addGuestOsMapping.html > >>> > >>> On Mon, Sep 20, 2021 at 3:25 AM Hean Seng wrote: > >>> > >>> > Hi > >>> > > >>> > Is there any way to add OS Type in ACS template ? Currently using > >>> 4.15 > >>> > > >>> > We need to add in as new OS is coming out , eg Debian 11, Ubuntu 20 > >>> etc. > >>> > > >>> > > >>> > -- > >>> > Regards, > >>> > Hean Seng > >>> > > >>> > >>> > >>> -- > >>> Daan > >>> > >> > >> > >> -- > >> Regards, > >> Hean Seng > >> > > > > > > -- > > Regards, > > Hean Seng > > > > > -- > Regards, > Hean Seng >
