xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Vasiliy G Tolstov <v.tolstov@selfip.ru>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: failed to start centos 5 domU with maxmem=30000
Date: Thu, 12 Aug 2010 16:24:05 +0400	[thread overview]
Message-ID: <1281615845.5454.20.camel@vase.work> (raw)
In-Reply-To: <042d87c1-bb13-436b-a5ba-9ec1578d53d0@default>

В Чтв, 12/08/2010 в 05:17 -0700, Dan Magenheimer пишет:
> > From: Vasiliy G Tolstov [mailto:v.tolstov@selfip.ru]
> > Sent: Thursday, August 12, 2010 5:38 AM
> > To: Pasi Kärkkäinen
> > Cc: xen-devel@lists.xensource.com
> > Subject: Re: [Xen-devel] failed to start centos 5 domU with
> > maxmem=30000
> > 
> > В Чтв, 12/08/2010 в 14:37 +0300, Pasi Kärkkäinen пишет:
> > > On Thu, Aug 12, 2010 at 02:24:05PM +0400, Vasiliy G Tolstov wrote:
> > > > Hello. I'm try to start centos domU pvm under sles 11 sp1 xen
> > kernel
> > > > with memory=512 and maxmem=30000. Centos doing boot and freeze.
> > > > If i'm try to use maxmem=15000 all works.
> > > >
> > > > Can You tell me what's wrong?
> > > >
> > >
> > > Is the centos PV domU 32bit or 64bit ?
> > 
> > 64 bit kernel-xen.
> > 
> > I found this in xen sources:
> > 
> > /* Simple continuous piecewiese linear function:
> >          *  max MiB -> min MiB  gradient
> >          *       0         0
> >          *      16        16
> >          *      32        24
> >          *     128        72    (1/2)
> >          *     512       168    (1/4)
> >          *    2048       360    (1/8)
> >          *    8192       552    (1/32)
> >          *   32768      1320
> >          *  131072      4392
> >          */
> > 
> > Why this is not provided in documentation or on web site?
> 
> Hi Vasily --
> 
> This function limits how far memory can be reduced when
> ballooning a guest (including dom0).  It is only a heuristic
> but is intended to take into account the various overheads
> a guest Linux kernel requires to manage memory to avoid
> out-of-memory conditions.
> 
> But I think you are correct... the same (or similar)
> function should be published as it also serves as a
> guideline for the ratio between memory= and maxmem=
> parameters when creating a guest:  If the ratio
> of maxmem divided by memory is too high, the guest
> will not even boot.
> 

Is that possible to use memory=32 and maxmem=60000 ?

> I am curious as to why you would specify memory= so
> much smaller than maxmem=.  Are you trying to overcommit
> memory for guests that are often idle but sometimes use
> a very large amount of memory?

We want to provide ability to use small as possible memory if the guest
is idle. And much as possible when the guest under heavy load.

Thank You.
-- 
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

  reply	other threads:[~2010-08-12 12:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 10:24 failed to start centos 5 domU with maxmem=30000 Vasiliy G Tolstov
2010-08-12 11:37 ` Pasi Kärkkäinen
2010-08-12 11:37   ` Vasiliy G Tolstov
2010-08-12 12:17     ` Dan Magenheimer
2010-08-12 12:24       ` Vasiliy G Tolstov [this message]
2010-08-12 18:00         ` Dan Magenheimer
2010-08-13  5:56           ` Vasiliy G Tolstov
2010-08-12 18:34         ` Jeremy Fitzhardinge
2010-08-13  5:54           ` Vasiliy G Tolstov
2010-08-13 15:19             ` Dan Magenheimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1281615845.5454.20.camel@vase.work \
    --to=v.tolstov@selfip.ru \
    --cc=dan.magenheimer@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).