<w...@widodh.nl <javascript:;>>
>> Sent: Friday, August 28, 2015 12:38 AM
>> To: dev@cloudstack.apache.org <javascript:;>
>> Subject: Re: Discuss reserving memory on KVM hypervisors ref:
>> CLOUDSTACK-8678
>>
>>
>>
>> Josh Hars
anything to add? Suggestions?
From: Wido den Hollander w...@widodh.nl javascript:;
Sent: Friday, August 28, 2015 12:38 AM
To: dev@cloudstack.apache.org javascript:;
Subject: Re: Discuss reserving memory on KVM hypervisors ref:
CLOUDSTACK-8678
Josh
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
.
Does anyone have anything to add? Suggestions?
From: Wido den Hollander w...@widodh.nl javascript:;
Sent: Friday, August 28, 2015 12:38 AM
To: dev@cloudstack.apache.org javascript:;
Subject: Re: Discuss reserving memory on KVM hypervisors ref
memory on KVM hypervisors ref: CLOUDSTACK-8678
Josh Harshman
Cloud Engineer
Intrinium
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
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.properties file and passed to the management server.
