From: Jacek Konieczny <jajcus@jajcus.net>
To: James Dingwall <james-xen@dingwall.me.uk>
Cc: xen-devel@lists.xen.org
Subject: Re: kernel log flooded with: xen_balloon: reserve_additional_memory: add_memory() failed: -17
Date: Thu, 20 Dec 2012 15:50:02 +0100 [thread overview]
Message-ID: <20121220145001.GC16443@jajo.eggsoft> (raw)
In-Reply-To: <d779abba78844d3701963b5ce5bdae92@imap.dingwall.me.uk>
On Wed, Dec 19, 2012 at 08:47:22AM +0000, James Dingwall wrote:
> Hi,
>
> I have encountered an apparently benign error on two systems where the
> dom0 kernel log is flooded with messages like:
>
> [52482.163855] System RAM resource [mem 0x1b8000000-0x1bfffffff] cannot
> be added
> [52482.163860] xen_balloon: reserve_additional_memory: add_memory()
> failed: -17
I have seen this bug too (under Xen 4.2.0).
I am using the following workaround to stop those messages:
cat /sys/devices/system/xen_memory/xen_memory0/info/current_kb > \
/sys/devices/system/xen_memory/xen_memory0/target_kb
I have not verified yet if Xen 4.2.1 is also affected.
Greets,
Jacek
next prev parent reply other threads:[~2012-12-20 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 8:47 kernel log flooded with: xen_balloon: reserve_additional_memory: add_memory() failed: -17 James Dingwall
2012-12-19 10:55 ` James Dingwall
2012-12-21 20:23 ` Konrad Rzeszutek Wilk
2013-01-02 10:28 ` James Dingwall
2012-12-20 14:50 ` Jacek Konieczny [this message]
2012-12-20 15:55 ` James Dingwall
2012-12-21 20:25 ` Konrad Rzeszutek Wilk
2012-12-23 10:41 ` Carsten Schiers
-- strict thread matches above, loose matches on Subject: below --
2012-12-24 14:39 Daniel Kiper
2013-01-24 21:38 ` Carsten Schiers
2013-01-25 10:48 Daniel Kiper
2013-01-28 16:36 ` Darren Shepherd
2013-01-28 17:40 ` David Vrabel
2013-01-29 11:53 Daniel Kiper
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=20121220145001.GC16443@jajo.eggsoft \
--to=jajcus@jajcus.net \
--cc=james-xen@dingwall.me.uk \
--cc=xen-devel@lists.xen.org \
/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.