Hi! Manually migrating VMs to the free host works (as long as I migrate at most two at once, I guess that the data moving between the local storages produces too much load otherwise). I also can deploy a VM on a specific host via CloudMonkey, but I'd love to see cloudstack choose a fitting host for me automatically.
Sadly I migrated lots of VMs yesterday to the free host such that each of the old full hosts now has <70% free memory, so for now I cannot reproduce the "cloudstack thinks there's free memory but there isn't" bug. But can I change the VM placement strategy, so that cloudstack no longer uses the first "free" host, but e.g. always the host _within_ a cluster with the least memory consumption? Just as the DeploymentPlanners are supposed to do _among_different_ clusters? Then all hosts would be used until the whole cluster is really "full". Ciao Martin -----Ursprüngliche Nachricht----- Von: Glenn Wagner [mailto:glenn.wag...@shapeblue.com] Gesendet: Freitag, 28. August 2015 07:48 An: users@cloudstack.apache.org Betreff: RE: Deployment failed on XenServer due to capacity miscalculation Hi, When you migrate the VM's manually to that Host does the process complete? Just a thought , what you could also do it add a service offering bind to the new host and deploy a VM to test it completes. Could you post a section of the Management server log file when you deploy the new VM? Glenn Wagner Senior Consultant, South Africa
