Hi Daniel,
Thanks for the reply. This clears a lot of things. I will test it out.
On Mon, 22 Nov 2021 at 18:57, Daniel Augusto Veronezi Salvador <
dvsalvador...@gmail.com> wrote:
> Hi Abishek,
> It's only available via CLI (at least, right now). There are some
> details that you need to pay
gt;
> Thanks,
> Harikrishna
>
> From: Abishek
> Sent: Sunday, November 21, 2021 12:19 PM
> To: users@cloudstack.apache.org
> Subject: Re: Dynamic VM Scaling KVM
>
> Hello All,
>
> I have successfully upgraded qemu-kvm to qemu-kvm-ev and now I can start
> the VM wi
Hi Abishek,
It's only available via CLI (at least, right now). There are some
details that you need to pay attention when dynamic scaling the VMs
(with KVM) and using the API:
(examples via CloudMonkey)
- The definitions that allow a VM (in KVM) to be dynamic scalable are
set in the XML
From: Abishek
Sent: Sunday, November 21, 2021 12:19 PM
To: users@cloudstack.apache.org
Subject: Re: Dynamic VM Scaling KVM
Hello All,
I have successfully upgraded qemu-kvm to qemu-kvm-ev and now I can start the VM
with dynamic-scaling template and service-offering(custom) unlike before
Hello All,
I have successfully upgraded qemu-kvm to qemu-kvm-ev and now I can start
the VM with dynamic-scaling template and service-offering(custom) unlike
before. But after successfully starting the VM I did not find any scaleVM
option in the Web UI while the VM is running. Is the feature only
Hi Slavka,
I am very grateful for the response. Can i directly proceed to replace
qemu-kvm with qemu-kvm-ev package. What effect will it have on my current
environment? If you could point me to any documentation regarding it I
would be extremely grateful.
Environment:
Hypervisor: Centos 7.9 KVM
I just forgot to mention that the working VM was deployed first with
qemu-kvm-ev (before switching to qemu-kvm for the tests), and the domain
XML had tag.
We had an offline conversation with Daniel, and we found that the memory
hotplug is included in qemu version 2.1.
Regards,
Slavka
On Fri,
Hi all,
I've tested the dynamic scaling with qemu-kvm and qemu-kvm-ev. Here are the
results for both with "Custom constrained" compute offering:
qemu-kvm-ev
deploy VM - passed
scale VM - passed
qemu-kvm
deploy VM - failed with the same error (org.libvirt.LibvirtException:
internal error:
Thanks a lot Wei for helping out. I will first try it in the Ubuntu
environment.
On Fri, 19 Nov 2021 at 00:09, Wei ZHOU wrote:
> Great, thanks Daniel.
>
> Abishek, now it seems you need to install qemu-kvm-ev for testing the
> feature.
>
> -Wei
>
> On Thursday, 18 November 2021, Daniel Augusto
Hi Daniel,
Thanks for the response. I will try with the ubuntu host in a separate test
environment. I do not want to replace qemu-kvm with qemu-kvm-ev as I am
uncertain what effect it will have in my current pre-production
environment(Cento-KVM). Shall I go with the default cloudstack
Great, thanks Daniel.
Abishek, now it seems you need to install qemu-kvm-ev for testing the
feature.
-Wei
On Thursday, 18 November 2021, Daniel Augusto Veronezi Salvador <
dvsalvador...@gmail.com> wrote:
> Hi Abishek, Wei, I tested this feature with Ubuntu 20.04 + KVM. Some
> community members
Hi Abishek, Wei, I tested this feature with Ubuntu 20.04 + KVM. Some
community members tested with CentOS7 and qemu-kvm-ev and it worked.
Also, as live snapshots and live migrations, hotplug memory is a known
limitation of qemu-kvm. I cannot give you advice regarding this
replacement too, as I
Hi Wei,
I am using Centos 7.9 with KVM.
Thank You.
On Wed, 17 Nov 2021 at 17:53, Wei ZHOU wrote:
> Hi Abishek,
>
> I cannot give your advice on it as I did not install qemu-kvm-ev to replace
> qemu-kvm before.
>
> I suspect that the issue you faced is caused by qemu-kvm. qemu-kvm-ev
>
Hi Abishek,
I cannot give your advice on it as I did not install qemu-kvm-ev to replace
qemu-kvm before.
I suspect that the issue you faced is caused by qemu-kvm. qemu-kvm-ev
supports more advanced features than qemu-kvm.
cc @Daniel, what hypervisor did you use to test the dynamic scaling ?
HI Wei,
I have not tested with qemu-kvm-ev. I am willing to try but what
effect will it have on my existing setup when I install qemu-kvm-ev in my
existing qemu-kvm. Should I have to remove qemu-kvm and install
qemu-kvm-ev? In the previous test I was able to start the machine with
Fixed Offering
Hi Abishek,
Have you tested with qemu-kvm-ev instead of qemu-kvm ?
-Wei
On Wed, 17 Nov 2021 at 10:00, Abishek wrote:
> 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,
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
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
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
23 matches
Mail list logo
