From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Florian Kirstein <xenlist@custom.ray.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Maximum number of DomUs? (x86_64)
Date: Sun, 9 Apr 2006 08:48:48 +0100 [thread overview]
Message-ID: <6aad2f79b9c716a166401acdc5cd141a@cl.cam.ac.uk> (raw)
In-Reply-To: <20060409033726.A9073@web.ray.net>
On 9 Apr 2006, at 02:37, Florian Kirstein wrote:
> So I wonder, which structure could run out of memory there? Is this a
> known
> limitation? Didn't find much about the maximum number of DomUs
> in the list archives... The Dom0 is running a CentOS4 x86_64 and I
> don't
> even need a DomU image to reach this limit, network and diskless DomUs
> just running into an "no root filesystem" panic being "preserve"d after
> the crash have the same effect.
Xen's own private heap is fixed size (16MB) and that's used to allocate
a certain amount of per-domain state. This restriction could be lifted
on x86/64 but it's not particularly a priority right now.
-- Keir
prev parent reply other threads:[~2006-04-09 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 1:37 Maximum number of DomUs? (x86_64) Florian Kirstein
2006-04-09 7:48 ` Keir Fraser [this message]
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=6aad2f79b9c716a166401acdc5cd141a@cl.cam.ac.uk \
--to=keir.fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xenlist@custom.ray.net \
/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.