From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: xen ballon errors in kernel logs even if I disabled it after kernel upgrade from 3.2 to 3.14 Date: Fri, 26 Sep 2014 13:02:11 +0100 Message-ID: <542555C3.1030606@citrix.com> References: <542529E3.9080104@m2r.biz> <54253E5C.5090002@citrix.com> <54255208.1080904@m2r.biz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54255208.1080904@m2r.biz> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Fabio Fantoni , xen-devel List-Id: xen-devel@lists.xenproject.org On 26/09/14 12:46, Fabio Fantoni wrote: > Il 26/09/2014 12:22, David Vrabel ha scritto: >> On 26/09/14 09:54, Fabio Fantoni wrote: >>> Yesterday I updated wheezy kernel (3.2) to 3.14 from wheezy-backports to >>> solves one critical network problem with new windows pv driver. >>> Today I saw the kernel logs full of this error: >>> xen:balloon: reserve_additional_memory: add_memory() failed: -17 >> Fixed by: >> >> 3dcf63677d4eb7fdfc13290c8558c301d2588fe8 (xen/balloon: cancel ballooning >> if adding new memory failed) >> >> Ballooned memory is required by backends which is why you're seeing it >> even with auto-ballooning disabled. >> >> David >> > > Thanks for your reply. > Is correct that show it also if dom0 have fixed memory size and xl.conf > have balloning disabled? Yes. > Can this problem cause a crash or other important aftermath? No. It's harmless. > Can you apply or request the backport of this fix to stable branchs? No. A fix for a harmless log message is not critical enough for stable. David