xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>,
	xen-devel@lists.xensource.com
Subject: Re: Abnormal memory usage of dom0 under Squeeze leading to crash
Date: Thu, 3 Feb 2011 09:34:13 +0100	[thread overview]
Message-ID: <20110203083413.GA19326@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <4D4A3F0C.6040607@debian.org>

[ Stripped debian-release from the recipients, this list is not for
dicussion ]

On Thu, Feb 03, 2011 at 01:37:16PM +0800, Thomas Goirand wrote:
> We normally run Lenny dom0 with 384 MB of RAM in our production server.

So do I:
| $ sudo xm dmesg | grep Comm
| (XEN) Command line: dom0_mem=384M
| $ sudo xm info
| [...]
| release                : 2.6.32-5-xen-amd64
| [...]
| xen_major              : 4
| xen_minor              : 0
| xen_extra              : .1
| [...]

> But as we did few trials with Squeeze, I had the very bad finding that a
> Squeeze dom0 requires at least 1024 MB of RAM. As soon as I do something
> like "xm mem-set Domain-0 800", my server crashes: OOM starts killing
> processes, starting with sshd, then mdadm and so on, then the server
> reboots by itself. This enormous amount of RAM isn't normal at all, and
> I am wondering what is happening.

Way not enough information. You are actually balooning the dom0 down?

Please provide all informations. xm dmesg, the kernel log, xm info.

> With both of the above, it's going to be easy to reproduce.

Nope. Works fine here.

>                                                             As Squeeze
> is said to be out in 3 days, it would be great to find out what's going
> on and fix asap.

There will be no fix for the initial release.

> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                                    Version                     Description
[...]

This looks more like a workstation then a minimal vm host.

Bastian

-- 
Star Trek Lives!

  reply	other threads:[~2011-02-03  8:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03  5:37 Abnormal memory usage of dom0 under Squeeze leading to crash Thomas Goirand
2011-02-03  8:34 ` Bastian Blank [this message]
2011-02-03  9:28   ` [Pkg-xen-devel] " Thomas Goirand
2011-02-03  9:35     ` Ian Campbell
2011-03-05  1:58       ` chris
2011-03-05  9:42         ` [Pkg-xen-devel] " Ian Campbell
2011-03-05 14:04           ` chris
     [not found]     ` <20110203102935.GA28521@wavehammer.waldi.eu.org>
2011-02-23  7:26       ` [Pkg-xen-devel] Strange behavior when doing xm mem-set Domain-0 (was: Abnormal memory usage of dom0 under Squeeze leading to crash) Thomas Goirand
2011-02-23  8:17         ` Ian Campbell

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=20110203083413.GA19326@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=pkg-xen-devel@lists.alioth.debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).