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.
> >
> >
>

Reply via email to