From: "Jérôme Petazzoni" <jp@enix.org>
To: xen-devel@lists.sourceforge.net
Subject: Problems with dom0 and low memory
Date: Tue, 07 Dec 2004 11:40:53 +0100 [thread overview]
Message-ID: <41B588B5.9010309@enix.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
I am running a Xen box where I need a lot of memory for a given domain
(which runs memory-hungry java apps). I had reduced the memory of
domain0 to 42000KB. It *seems* that after running OK for a while, a low
memory condition on domain0 messed during a short time the VBD of the
other domains, and they got a burst if I/O errors. After this event, the
other domains were still running, and their VBD were still working, but
the burst of I/O errors aborted the ext3 journal on the filesystems
(causing them to go read-only).
Here are the kernel logs of both domains if you want to check that it's
indeed a low memory condition problem and not something else (which
would then be a "real" bug).
I increased the memory allocated to domain0, but it would be interesting
to know if there is a way to avoid those problems (I thought about
increasing /proc/sys/vm/min_free_kbytes ; would it be useful here?)
The dom0 and domU kernels, as well as xen itself, the associated
symbols, and the same log files are located here, if someone needs them:
http://skaya.enix.org/webs/xen/dom0-lowmem/
[-- Attachment #2: dom0-kern.log.gz --]
[-- Type: application/gzip, Size: 14000 bytes --]
[-- Attachment #3: domU-kern.log.gz --]
[-- Type: application/gzip, Size: 566 bytes --]
next reply other threads:[~2004-12-07 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 10:40 Jérôme Petazzoni [this message]
2004-12-07 12:51 ` Problems with dom0 and low memory Peri Hankey
2004-12-07 17:35 ` Keir Fraser
2004-12-07 19:47 ` Derek Glidden
2004-12-07 21:47 ` Jérôme Petazzoni
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=41B588B5.9010309@enix.org \
--to=jp@enix.org \
--cc=xen-devel@lists.sourceforge.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.