Just to add some context, this was awhile back that I tried it, years. The
idea was that we could just set max memory to some crazy high number and
then “unlock” just the amount in the offering, and adjust on the fly. As
mentioned I found it was trivial for VM users to unlock the full amount and
ge
Yes, it puts memory pressure within the VM to evict the memory and then it
is hidden from the OS.
However, I’m not a fan of ballooning, as it depends on a driver in the
guest OS. When I tested it a few years back one simply had to blacklist the
module within the VM to get the full (max) RAM, as th
Hi Andrija,
I tried scaling down memory, it worked on my test VM. I don't think it should
cause VM or apps to crash if libvirt allows.
Regards.
Regards,
Rohit Yadav
From: Andrija Panic
Sent: Wednesday, September 11, 2019 2:11:22 PM
To: dev
Subject: Re: Dynami
I've created a work-in-progress PR for this:
https://github.com/apache/cloudstack/pull/3595
Regards,
Nicolas Vazquez
From: Andrija Panic
Sent: Wednesday, September 11, 2019 6:11 PM
To: dev
Subject: Re: Dynamic scaling support for KVM
Correct Rohit - but we w
Correct Rohit - but we will not support scaling down the MEM (nor CPU),
since OS will crash, since there is no working ballooning driver (you need
to use ballooning device (check) and the driver inside OS - which is an
abandoned project - I have pinged an RHEL engineer for this, and he
explicitly c
I hope this features is implemented in near future.
Regards
On Wed, Sep 11, 2019 at 11:53 PM Rohit Yadav
wrote:
> I tried this:
>
> The domain XML needs to say what is the current allocation of vcpus or
> memory and what is the max. value:
> 8392704
> 4194304
> 4
>
> Then, using virsh I c
I tried this:
The domain XML needs to say what is the current allocation of vcpus or memory
and what is the max. value:
8392704
4194304
4
Then, using virsh I could dynamically scale/up/down the vcpus and memory:
virsh setmem 6G
virsh setvcpus 4
This changed the value in domain XML for t
