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
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
Hi everyone,
currently I am trying myself on upgrading my cloudstack environment from
4.15.2 to 4.16.
I am a bit puzzeled as, while upgrading via repositorys i get the
notification / question, if i want to use my "old" configuration files on
the Management Server. Or use the newly provided from
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 wrote:
> HI Daniel,
>
> Extremely glad to hear that dynamic scaling is now supported in
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
Hi Abishek, It's already supported. The error you reported seems to be
related to (according to logs presented by you) insufficient capacity of
the environment when deploying the VM. It could be related to a lack of
network (like DHCP) or compute (like RAM or CPU) resources, could you
provide
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
Hi Mohamad,
Firstly, welcome to the CloudStack community.
The short answer I can say we have a feature called "VM ingestion" using which
we can import existing VMs from vCenter into CloudStack. You can have a quick
look at this blog
Hello,
First time user here,
We have private cloud setup in our company using vmware with only vcenter
for management, I'm considering adding cloudstack to the mix.
The question is how disruptive would this be to the environment ? do we have
to build it from scratch or is it possible
`out of band` means operations done outside CloudStack (and CloudStack doesn’t
know about it).
You can add custom attributes to VMware object. CloudStack would only refer /
modify the attributes it adds.
Regards,
Suresh
On 16/11/21, 8:17 AM, "小林 美佳子" wrote:
Thanks for the reply.
I
10 matches
Mail list logo
