Hi Martin, Thanks for the information.
From the details below, I understand that your Cluster will not allow additional VMs to be created if 85% of the memory is consumed. This value is important as you also need to factor in what amount of memory is required by the Hypervisor (XenServer) to run. Xenserver needs a minimum of 1GB -- Check out the following link: http://support.citrix.com/servlet/KbServlet/download/34970-102-704220/installation.pdf. Secondly, unless you are running memory intensive applications, using a 1:1 ratio is not entirely economically viable, you can safely up the mem.overprovisioning.factor to 2 or 4 (depending on your Memory over provisioning calculations vs CPU). This means that you are essentially doubling or quadrupling up on the actual amount of memory you have available. Another option to look at is your deployment.planners.order & vm.deployment.planner fields. In my case, I use FirstFitPlanner for both as we prefer to fully utilize each host before provisioning on another host. Kind Regards, Timothy Lothering Timothy Lothering Solutions Architect Managed Services T: +27877415535 F: +27877415100 C: +27824904099 E: tlother...@datacentrix.co.za DISCLAIMER NOTICE: Everything in this e-mail and any attachments relating to the official business of Datacentrix Holdings Ltd. and its subsidiaries ('Datacentrix') is proprietary to Datacentrix. It is confidential, legally privileged and protected by law. Datacentrix does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of Datacentrix. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Datacentrix cannot assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. -----Original Message----- From: Martin Emrich [mailto:martin.emr...@empolis.com] Sent: 08 July 2015 01:45 PM To: users@cloudstack.apache.org Subject: AW: Deployment failed on XenServer due to capacity miscalculation Hi! The config options are on their default value: mem.overprovisioning.factor = 1 cluster.memory.allocated.capacity.disablethreshold = 0.85 (Would affect the whole cluster capacity, not that of a single host) So nothing strange here. I un- and remanaged the cluster, but no change in numbers :( Also there were no interesting log messages... Thanks Martin -----Ursprüngliche Nachricht----- Von: Timothy Lothering [mailto:tlother...@datacentrix.co.za] Gesendet: Mittwoch, 8. Juli 2015 12:34 An: users@cloudstack.apache.org Betreff: RE: Deployment failed on XenServer due to capacity miscalculation Hi Martin, I have seen this before with our CXS environment too. Could of things to check: 1. What is the mem.overprovisioning.factor field set to? 2. What is the cluster.memory.allocated.capacity.disablethreshold field set to? Also, try unmanage the XS Cluster, wait a couple of minutes and re-manage it. Timothy Lothering Solutions Architect Managed Services T: +27877415535 F: +27877415100 C: +27824904099 E: tlother...@datacentrix.co.za DISCLAIMER NOTICE: Everything in this e-mail and any attachments relating to the official business of Datacentrix Holdings Ltd. and its subsidiaries ('Datacentrix') is proprietary to Datacentrix. It is confidential, legally privileged and protected by law. Datacentrix does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of Datacentrix. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Datacentrix cannot assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. -----Original Message----- From: Martin Emrich [mailto:martin.emr...@empolis.com] Sent: 08 July 2015 12:17 PM To: users@cloudstack.apache.org Subject: AW: Deployment failed on XenServer due to capacity miscalculation Hi! I tried that ("force reconnect"). But no improvement: Via cloudmonkey, memorytotal-memoryallocated == 4302535168, that's 4103MB. Via XenServer, the host has only 1667 MB free memory. Restarting the management server does not solve it, either. I see this: 2015-07-08 12:03:40,612 DEBUG [c.c.c.CapacityManagerImpl] (CapacityChecker:ctx-6c463573) Found 74 VMs on host 335 2015-07-08 12:03:40,641 DEBUG [c.c.c.CapacityManagerImpl] (CapacityChecker:ctx-6c463573) Found 2 VM, not running on host 335 2015-07-08 12:03:40,643 DEBUG [c.c.c.CapacityManagerImpl] (CapacityChecker:ctx-6c463573) No need to calibrate cpu capacity, host:335 usedCpu: 226500 reservedCpu: 0 2015-07-08 12:03:40,643 DEBUG [c.c.c.CapacityManagerImpl] (CapacityChecker:ctx-6c463573) No need to calibrate memory capacity, host:335 usedMem: 124528885760 reservedMem: 0 My current "workaround" is to disable the host in ACS, then the deployment planner takes the other host with enough free memory, but that's not a permanent solution. Ciao Martin -----Ursprüngliche Nachricht----- Von: Nick Brody [mailto:nickbrody2...@gmail.com] Gesendet: Mittwoch, 8. Juli 2015 12:05 An: users@cloudstack.apache.org Betreff: Re: Deployment failed on XenServer due to capacity miscalculation hi martin, Make sure that you reconnect server
