From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jacek Konieczny <jajcus@jajcus.net>
Subject: Re: kernel log flooded with: xen_balloon:
 reserve_additional_memory: add_memory() failed: -17
Date: Thu, 20 Dec 2012 15:50:02 +0100
Message-ID: <20121220145001.GC16443@jajo.eggsoft>
References: <d779abba78844d3701963b5ce5bdae92@imap.dingwall.me.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <d779abba78844d3701963b5ce5bdae92@imap.dingwall.me.uk>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: James Dingwall <james-xen@dingwall.me.uk>
Cc: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

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