Hello Wei, I am very grateful for your response. In my test environment I first created a service offering of Custom Constrained (minCore=1, maxCore=10, minRam=1GB, maxRam=12GB, CPUSpeed=2000) with dynamic scaling enabled. But every time I tried to start the VM under this ServiceOffering I got the above mentioned error. Please find the following agent log for that particular VM:
https://controlc.com/4618c4d8 HOST OS : Centos 7.9 QEMU: QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-175.el7_9.4), Copyright (c) 2003-2008 Fabrice Bellard And I think the error seems to be with the service offering (Custom Constrained). So, I created two Fixed services offering A(1 core and 1GB) and B(2 Core and 2 GB) with dynamic scaling enabled. I then built a VM based on service offering A and the VM started(finally). But I did not find any option to scale the VM while it's running. I was only able to scale the VM to shutdown state. Thank You. On Wed, 17 Nov 2021 at 13:11, Wei ZHOU <ustcweiz...@gmail.com> wrote: > Hi Abishek, > > I guess the error is same as before: > > qemu: invalid ram size: size=4194304k,slots=16,maxmem=1583660032k > > > What are your hypervisor/qemu version and guest OS version ? > Can you check agent.log and share the xml definition of the vm ? > > -Wei > > On Wed, 17 Nov 2021 at 05:18, Abishek Budhathoki <abckd...@gmail.com> > wrote: > > > Hello Wei, > > > > I have also tested with limited service offering where max RAM is 12GB > and > > CPU is 12 core. But the result is the same. I can not start the VM. But > if > > I turn off Dynamic Scaling to Off on Advance Mode while creating the > > instance I can start the VM. > > > > Thank You. > > > > On Tue, 16 Nov 2021 at 20:50, Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > > > The max ram looks very huge. It would be better to double check the > > > offerings. > > > > > > "minRam":"(4.00 GB) 4294967296","maxRam":"(1.4749 TB) 1621666836480" > > > > > > > > > -Wei > > > > > > > > > On Tue, 16 Nov 2021 at 15:21, Abishek Budhathoki <abckd...@gmail.com> > > > wrote: > > > > > > > HI Daniel, > > > > > > > > Extremely glad to hear that dynamic scaling is now supported in KVM. > > > > > > > > There is no issue of resources. I cannot start a VM with dynamic > > scaling > > > > enabled template and service offering. But I am able to start other > > VMs. > > > I > > > > have shared the logs on > > > > > > > > https://controlc.com/204f727d > > > > > > > > Thank You > > > > > > > > On Tue, 16 Nov 2021 at 16:51, Abishek Budhathoki <abckd...@gmail.com > > > > > > wrote: > > > > > > > > > Hello All, > > > > > > > > > > I have just upgraded my Cloudstack installation from 4.15 to 4.16 > and > > > > > everything is working as expected. In the docs site(Changes in > > 4.16.0.0 > > > > > since 4.15) I have seen that dynamic Scaling with KVM now works > with > > > > > Cloudstack 4.16(github #4878 Support vm dynamic scaling with kvm). > Is > > > > this > > > > > true? I have tried to test this but was unsuccessful. Changed > > > > > global setting enable dynamic scaling to true, created template > with > > > > > dynamic scaling support, created service offering that supports > > dynamic > > > > > Scaling. > > > > > I only see the following error: > > > > > ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-12:ctx-bb24d685 > > > > > job-2304) (logid:394001c9) Unexpected exception while executing > > > > > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin > > > > > com.cloud.utils.exception.CloudRuntimeException: Unable to start a > VM > > > due > > > > > to insufficient capacity > > > > > > > > > > If it's not still supported please discard this email. > > > > > > > > > > Thank You. > > > > > > > > > > > > > > > > > > > >
