From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com, Michal Novotny <minovotn@redhat.com>
Subject: Re: [PATCH] Domain creation 4MB memory allocation
Date: Wed, 01 Apr 2009 10:06:58 +0100 [thread overview]
Message-ID: <49D34AD2.76E4.0078.0@novell.com> (raw)
In-Reply-To: <49D31CA1.4090103@redhat.com>
>>> Michal Novotny <minovotn@redhat.com> 01.04.09 09:49 >>>
>Hi,
>I've found some problems when running 2 guests with and then trying to
>install a new machine (no matter whether using virt-manager or
>virt-install). I am attaching a patch that fixes this problem.
>
>I was working on 8G box and I have done those things:
> 1. xm create PVguest maxmem=2500 memory=2500
> 2. xm create FVguest maxmem=2500 memory=2500
> 3. virt-install -l http://path/to/install/ -r 2500 -v --nodisks -n
>someGuestName
>
>Before applying this patch it returned "Cannot allocate memory" error
>but after applying my patch it created a new domain and started
>installation well but it's reproducible sometimes and not everytime.
This is just curing (actually not really curing, just reducing the likelihood of
its occurrence) a symptom, rather than the root cause: What if 4Mb turn
out to be insufficient for someone else on some other machine? In order
to guarantee hvm guest creation to be possible (at least in the case
where shadow paging is to be used - not sure about NPT/EPT's
requirements), there has to be a way to guarantee some small amount
of contiguous memory being available in Xen. Ballooning cannot guarantee
this, and after a longer period of up-time with many guests starting and
dying even using dom0_mem= on the Xen command line doesn't help due
to fragmentation being unavoidable.
Jan
next prev parent reply other threads:[~2009-04-01 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 7:49 [PATCH] Domain creation 4MB memory allocation Michal Novotny
2009-04-01 9:06 ` Jan Beulich [this message]
2009-04-01 9:48 ` Michal Novotny
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=49D34AD2.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=minovotn@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.