From: Anthony Wright <anthony@overnetdata.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Memory allocation going seriously wonky on 4.1.1
Date: Fri, 30 Sep 2011 16:07:06 +0100 [thread overview]
Message-ID: <4E85DB1A.5060606@overnetdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
I have a machine with 16GB of RAM running 32 bit xen 4.1.1 with Dom0
running a 3.0.4 linux kernel and 23 paravirtualized DomUs.
As the free ram gets to 2391 MB free the system behaves as if it's got
no more ram, and starts grabbing ram from Dom0, before getting even more
confused and failing to start DomUs and eventually crashing the whole
machine. I have attached a tarball with the output of xl dmesg, xl info
& xl list at various points.
Stage 1
Everything is fine, Dom0 has 2000MB according to xl list, and 'xl info'
says there is 2405MB free.
Stage 2
I have increased the memory for the DomU labelled 10-4 from 700MB to
1000MB, Dom0 has 1713MB and 'xl info' says there is 2391MB free.
Stage 3
I have tried to increase the memory for the DomU labelled 13-4 from
700MB to 1000MB, but it failed on the 'xl create' displaying the message
'failed to free memory for the domain'. Dom0 has 1413MB and 'xl info'
says there is 3391MB free.
State 4
I tried to create the 13-4 DomU again, and this time it succeeds. Dom0
has 1413MB and 'xl info' says there is 2391MB free.
If I repeatedly stop and start DomUs at this point, particularly if I
request more ram, the machine locks up. This may be due to lack of Dom0 ram.
[-- Attachment #2: vm-memory-logs.tar.bz2 --]
[-- Type: application/octet-stream, Size: 4445 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-09-30 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 15:07 Anthony Wright [this message]
2011-10-01 12:07 ` Memory allocation going seriously wonky on 4.1.1 Pasi Kärkkäinen
2011-10-03 13:45 ` Anthony Wright
2011-10-03 19:09 ` Konrad Rzeszutek Wilk
2011-10-06 12:57 ` Anthony Wright
2011-10-06 15:48 ` Konrad Rzeszutek Wilk
2011-10-06 15:51 ` Anthony Wright
2011-10-06 14:59 ` Anthony Wright
2011-10-03 13:55 ` Anthony Wright
2011-10-03 19:10 ` Konrad Rzeszutek Wilk
2011-10-06 14:05 ` Anthony Wright
2011-10-06 15:48 ` Konrad Rzeszutek Wilk
2011-10-03 19:04 ` Konrad Rzeszutek Wilk
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=4E85DB1A.5060606@overnetdata.com \
--to=anthony@overnetdata.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.