From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: Strange memory balloning problem even if balloning is disabled Date: Mon, 2 Mar 2015 16:31:01 +0000 Message-ID: <54F49045.3000008@citrix.com> References: <54F48726.8000006@m2r.biz> <54F49CA10200007800065406@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54F49CA10200007800065406@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Fabio Fantoni Cc: Anthony PERARD , xen-devel@lists.xen.org, Wei Liu , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 02/03/15 16:23, Jan Beulich wrote: >>>> On 02.03.15 at 16:52, wrote: >> On systems with wheezy as dom0 and kernel 3.2 it seems there are no >> visible problems. >> After updating the kernel to 3.16 (from backports repository), after >> starting the domUs, I get many of these errors in syslog and kern.log >> (infinite loop): >> xen:balloon: Cannot add additional memory (-17) > > I have a vague recollection of some fix from David aiming at > avoiding to issue this message, but you would clearly have better > luck getting a qualified response if you Cc-ed kernel people when > reporting kernel problems (assuming you need explicit Cc-s at all, > as most relevant people read the list anyway afaik) - I certainly > can't figure by what criteria you put together the Cc list. You need 3dcf63677d4eb7fdfc13290c8558c301d2588fe8 (xen/balloon: cancel ballooning if adding new memory failed) fd8b79511349efd1f0decea920f61b93acb34a75 (xen/balloon: Don't continue ballooning when BP_ECANCELED is encountered) Or you can disable CONFIG_XEN_BALLOON_MEMORY_HOTPLUG. David