[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] xen ballon errors in kernel logs even if I disabled it after kernel upgrade from 3.2 to 3.14
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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |