Created attachment 626993 [details]
Description of problem:
"Max free Memory for scheduling new VMs" is reporting negative values.
Version-Release number of selected component (if applicable):
Using a 16GB host, I've added 2 VM's with 8GB each (of which 4GB are guaranteed), and ran them.
>> vdsClient -s 0 getVdsCaps | grep memSize
memSize = 15829
>> vdsClient -s 0 getVdsCaps | grep reservedMem
reservedMem = 321
With those numbers, I got:
Max free Memory for scheduling new VMs = -1006 MB
This may happen due to over commit being just an estimation for the actual consolidation capabilities. However any negative value in calculation should be translated to 0 on the value reported to the UI and API.
The negative value seems expected. According with BZ#846677, the field calculation formula is:
( over commit * host memory )
( host memory committed + host reserved )
In your case, if overcommit policy is "no overcommit", you need to add 1518 MB to host in order to run a new VM with Physical Memory Guaranteed = 512 MB, for example. Or change the overcommit policy.
OK - SI23
"Max free Memory for scheduling new VMs" no longer reports negative values - reports 0 instead.