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:[email protected]]
Gesendet: Mittwoch, 8. Juli 2015 12:05
An: [email protected]
Betreff: Re: Deployment failed on XenServer due to capacity miscalculation
hi martin, Make sure that you reconnect server
