n: Somesh Naidu [mailto:somesh.na...@citrix.com]
Gesendet: Montag, 27. Juli 2015 18:40
An: users@cloudstack.apache.org
Betreff: RE: Deployment failed on XenServer due to capacity miscalculation
This is mostly due to incorrect calculation of XS memory overhead calculation
by cloudstack. However, it i
way it is meant to be...
>>
>> Ciao
>>
>> Martin
>>
>> -Ursprüngliche Nachricht-
>> Von: Somesh Naidu [mailto:somesh.na...@citrix.com]
>> Gesendet: Montag, 27. Juli 2015 18:40
>> An: users@cloudstack.apache.org
>> Betreff: RE: Deployment fa
omesh Naidu [mailto:somesh.na...@citrix.com]
> Gesendet: Montag, 27. Juli 2015 18:40
> An: users@cloudstack.apache.org
> Betreff: RE: Deployment failed on XenServer due to capacity miscalculation
>
> This is mostly due to incorrect calculation of XS memory overhead
> calculation b
hricht-
Von: Stephan Seitz [mailto:s.se...@secretresearchfacility.com]
Gesendet: Sonntag, 12. Juli 2015 22:52
An: users@cloudstack.apache.org
Betreff: Re: Deployment failed on XenServer due to capacity miscalculation
Hi there,
despite not reading the whole thread, I'ld assume that there'
Hi there,
despite not reading the whole thread, I'ld assume that there's simple no
single memory segment of the requested size available at your particular
xenserver.
Just keep in mind, that Xen partitions memory and - after long run -
could not assign a contiguous block, even if the sum of all se
Hi!
Am 10.07.2015 um 16:42 schrieb Timothy Lothering:
Hi Martin,
From the logs it seems that ACS has found that the host has sufficient memory
capacity, but when it deploys it, it seems there is not enough. It could be a
bug whereby technically the system has enough capacity, but during the
--Ursprüngliche Nachricht-
Von: Timothy Lothering [mailto:tlother...@datacentrix.co.za]
Gesendet: Freitag, 10. Juli 2015 13:12
An: users@cloudstack.apache.org
Betreff: RE: Deployment failed on XenServer due to capacity miscalculation
Thanks Martin,
Could you please dump your full logs somewhere so w
Thanks Martin,
Could you please dump your full logs somewhere so we can look into this further?
-Original Message-
From: Martin Emrich [mailto:martin.emr...@empolis.com]
Sent: 09 July 2015 03:49 PM
To: users@cloudstack.apache.org
Subject: Re: Deployment failed on XenServer due to
Hi!
Am 08.07.2015 um 16:15 schrieb Timothy Lothering:
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 amoun
twoch, 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?
yment
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: Deploy
hi martin, Make sure that you reconnect server
On Tue, Jul 7, 2015 at 4:33 AM, Martin Emrich
wrote:
> Hi!
>
>
>
> I try to create an instance on my ACS (4.4.3, XenServer 6.2 SP1). The
> deployment fails on the first host in the cluster, as its memory is nearly
> full.
>
>
>
> I see this message
12 matches
Mail list logo