From: Florian Kirstein <xenlist@custom.ray.net>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Maximum number of DomUs? (x86_64)
Date: Sun, 9 Apr 2006 03:37:26 +0200 [thread overview]
Message-ID: <20060409033726.A9073@web.ray.net> (raw)
Hallo,
I just tried to push a quad-opteron server with 16GB of memory to the limit
and I reached it a bit earlier than expected. It seems that no matter
how much memory I assign to each DomU, and wether i use loopback or
phy/lvm devices for the storage, or no vif/storage at all, I can't
crate more than 107 DomUs (yes, that's not a real problem, I'm just
curious :) After No. 107 that I get(*):
Using config file "vm107".
Started domain VM107
Using config file "vm108".
Error: (12, 'Cannot allocate memory')
Using config file "vm109".
Error: (12, 'Cannot allocate memory')
but of course there's still memory left in Domain-0 to balloon out:
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 9215 4 r----- 319.3
VM1 1 64 1 ------ 0.8
VM10 10 64 1 -b---- 0.7
VM100 100 64 1 -b---- 0.4
When I assign 128MB per DomU exactly the same effect:
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 2372 4 r----- 2196.3
VM1 129 128 1 -b---- 0.4
VM10 138 128 1 -b---- 0.4
VM100 228 128 1 -b---- 0.2
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.
(:ul8er, r@y
(*) yes, I know, I could have used a vmid parameter instead of creating
100s of configfiles :)
next reply other threads:[~2006-04-09 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 1:37 Florian Kirstein [this message]
2006-04-09 7:48 ` Maximum number of DomUs? (x86_64) Keir Fraser
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=20060409033726.A9073@web.ray.net \
--to=xenlist@custom.ray.net \
--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.