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:26 AM, "Yiping Zhang" <[email protected]> wrote: >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 to reflect updated memory allocations >without restarting every single VM instances? > >While I am on the subject of restarting VM instances, I went into data >base to get their POWER_STATE_UPDATE_TIME value from vm_instance table >directly. I noticed that this value is not consistently updated for those >VM instances I restarted (either in UI or via API calls with stop >followed by start actions). Is this a bug ? > >Yiping DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Accelerite, a Persistent Systems business. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent Systems business does not accept any liability for virus infected mails.
