RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on XenServer

2015-01-27 Thread Yuri Kogun
Thank you, Somesh  Will try to upgrade. Best regards  Yuri  From: somesh.na...@citrix.com To: users@cloudstack.apache.org Subject: RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on XenServer Date: Mon, 26 Jan 2015 18:49:54 +

RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on XenServer

2015-01-26 Thread Yuri Kogun
Hi Somesh,  Thank you for the reply, yes I found the issue in the Jira.  The affected host was running about 31 VM's and we don't use memory  over provisioning at all.  Unfortunately cloudstack fails to restart he VM and it is a big issue for us as the restart is a part of a nightly job and we

RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on XenServer

2015-01-26 Thread Somesh Naidu
Yes, seen this quite a few times. I believe you already found CLOUDSTACK-2344. Basically, the issue happens when cloudstack's view of available memory is out of sync (more) than that of XS. This could happen due to incorrect calculation of memory overhead and Dom0 memory. It is also possible

RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on XenServer

2015-01-26 Thread Somesh Naidu
Yes, XS will have the correct view since it is the one that's managing the memory. The problem is the way CS calculates the memory overhead. I don't think there is much we can do in terms of configuration. This is how CS arrives at total ram: ram = (long)((ram - dom0Ram - _xsMemoryUsed) *