1-You need to stop-start vm for the real changes (to change vm settings at
hypervisor level).
2-if you want to change available resources at DB level try updating
cpu/mem overprovisioning column in user_vm_details and cluster_details I
never tried this but it should work .
~prashant
On 3/3/16, 6:
Hi,
I have to change the global and cluster setting memory.overprovisioning.factor
for one of clusters with hundreds of running VM instances. Now, in order for
the changes to take effect, I need to restart all running instances. I am
wondering is there a way to update all running VM instances
So I've taken the same lab and I enabled usage on it. Resulting database is
about 200MB total (both cloud and cloud_usage).
To address your other questions ...
>It would seem that the 250GB suggested by the installation documents is
>somewhat of an overkill. Would it be possible to simply >u
