global setting "host.reservation.release.period" dictates for how long the host will reserve a capacity for a stopped VM.
I assume (though I find this idea a bit stupid IMO) that idea was if you stop VM, but you are short on capacity, nobody else can "jump in" and deploy a new VM taking the rest of the host's free capacity, so you (as a long-standiong customer/user) now can't start your VM you stopped 5mins ago. Best, On Tue, 8 Jun 2021 at 17:25, Kalil de Albuquerque Carvalho < [email protected]> wrote: > Hello all. > > I'm testing Cloudstack 4.15 and it is strange, or, probably, I'm doing > same mistakes, that when I halted my VM's the resources are not been > released for the system. It is like when the VM is created the resource > it is reserved exclusively for it. > > Some one can tell me where I can find the documentation that I can get > this information and how to work with it? > > Any one can help me to understand what it is happening? > > Best regards. > > -- Andrija Panić
