x27;t have automation setup for testing, etc.
Kevin McCormick
Director of Cloud Services
Intrinium
-Original Message-
From: Remi Bergsma [mailto:rberg...@schubergphilis.com]
Sent: Friday, August 28, 2015 23:41
To:
Subject: Re: Discuss reserving memory on KVM hypervisors ref: CLOUDSTACK-86
t; I've forked the repo and am working on a fix.
>> Does anyone have anything to add? Suggestions?
>>
>>
>> From: Wido den Hollander >
>> Sent: Friday, August 28, 2015 12:38 AM
>> To: dev@cloudstack.apache.org
&g
on a fix.
> Does anyone have anything to add? Suggestions?
>
>
> From: Wido den Hollander >
> Sent: Friday, August 28, 2015 12:38 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Discuss reserving memory on KVM hypervisors ref:
>
calculating the ram available.
I've forked the repo and am working on a fix.
Does anyone have anything to add? Suggestions?
From: Wido den Hollander
Sent: Friday, August 28, 2015 12:38 AM
To: dev@cloudstack.apache.org
Subject: Re: Discuss reserving memory o
On 27-08-15 18:36, Josh Harshman wrote:
> In a KVM cluster, CloudStack sees 100% of the compute node's RAM and treats
> it as allocatable space which eventually leads to OOM killing guests.
>
>
> There is an agent property named host.reserved.mem.mb which is able to be set
> in the agent.prop
