From: David Vrabel <david.vrabel@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>,
xen-devel <xen-devel@lists.xensource.com>
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 11:22:20 +0100 [thread overview]
Message-ID: <54253E5C.5090002@citrix.com> (raw)
In-Reply-To: <542529E3.9080104@m2r.biz>
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
next prev parent reply other threads:[~2014-09-26 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 8:54 xen ballon errors in kernel logs even if I disabled it after kernel upgrade from 3.2 to 3.14 Fabio Fantoni
2014-09-26 10:22 ` David Vrabel [this message]
2014-09-26 11:46 ` Fabio Fantoni
2014-09-26 12:02 ` David Vrabel
2014-12-11 9:40 ` Fabio Fantoni
2014-12-11 10:48 ` David Vrabel
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=54253E5C.5090002@citrix.com \
--to=david.vrabel@citrix.com \
--cc=fabio.fantoni@m2r.biz \
--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).