Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: <5530feba9f1d4a84bb55ac20ae0d455e@ILLDCUC11.Intrinium.local>
References: <8a1d073420b444daaf71a4ee615f8c11@ILLDCUC11.Intrinium.local>
	<55E01003.4090505@widodh.nl>
	<5530feba9f1d4a84bb55ac20ae0d455e@ILLDCUC11.Intrinium.local>
Date: Sat, 29 Aug 2015 07:49:34 +0200
Message-ID: 
 <CAP997UdmzNtq4_FFZv5HUG6rUuz_mkNCnT7o37BPkhpCmQWRoA@mail.gmail.com>
Subject: Re: Discuss reserving memory on KVM hypervisors ref: CLOUDSTACK-8678
From: Erik Weber <terbolous@gmail.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=f46d04428804d2804d051e6cc3e6

--f46d04428804d2804d051e6cc3e6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Make it configurable to enable/disable the check? Or even the size.

For labs etc you might not have or want that much to spare.


Erik

Den l=C3=B8rdag 29. august 2015 skrev Josh Harshman <Josh.Harshman@intriniu=
m.com>
f=C3=B8lgende:

> Wido -
> Looks like the problem resides in the logic that does the detection of th=
e
> host resources.  It looks like most, if not all, the KVM host detection
> occurs in the LibvirtComputingResource class.  Here I can modify it so it
> will take the value stored in dom0MinMem into account when calculating th=
e
> ram available.
>
> I've forked the repo and am working on a fix.
> Does anyone have anything to add?  Suggestions?
>
> ________________________________________
> From: Wido den Hollander <wido@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 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 gues=
ts.
> >
> >
> > 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.
> This value is stored as dom0MinMem, however, it appears to be ignored.
> >
> >
> > If we could tweak the host capacity calculation and have it take this
> into account, I believe that would be ideal.
> >
> >
> > Side note: the variable dom0MinMem is declared as an int and can be
> overflowed. Suggested change would be make it a long and add a check
> especially if we are going to make this a configurable parameter.
> >
> >
>
> Yes, that seems like a sane thing to do. We should be able to say that
> eg 8GB of memory should stay available for the HV.
>
> Don't know where the problem lies though. A PR is welcome :)
>
> Wido
>
> >
> >
> > Josh Harshman
> >
> > Cloud Engineer
> >
> >
> > Intrinium
> > Tel: (509) 465-1234 x5259
> > Fax: (866) 565-4578
> > Lync / Skype: Josh.Harshman@intrinium.com <javascript:;>
> > Web: http://intrinium.com<http://intrinium.com/>
> >
> >
> > [Intrinium Long Sig Logo]<http://intrinium.com/>
> >
> >
> > [Facebook]<http://www.facebook.com/pages/intrinium/154891544582822>
> [Twitter] <http://twitter.com/intrinium>  [Linkedin] <
> http://www.linkedin.com/company/intrinium_networks_it_security?trk=3Dfc_b=
adge>
> [Youtube] <http://www.youtube.com/user/intrinium>  [Blog] <
> http://intrinium.com/blog/>
> >
> > Information Security and Compliance Consulting | Managed IT and Securit=
y
> Services | Cloud Services
> >
> >
> >
> >
> >
> > ________________________________
> >
> > This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this email in error please notify the
> system manager. This message contains confidential information and is
> intended only for the individual named. If you are not the named addresse=
e
> you should not disseminate, distribute or copy this e-mail. Please notify
> the sender immediately by e-mail if you have received this e-mail by
> mistake and delete this e-mail from your system. If you are not the
> intended recipient you are notified that disclosing, copying, distributin=
g
> or taking any action in reliance on the contents of this information is
> strictly prohibited.
> >
>

--f46d04428804d2804d051e6cc3e6--