From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Shuklin Subject: Re: a ton of kernel issues Date: Thu, 15 Dec 2011 16:45:41 +0400 Message-ID: <4EE9EBF5.8000402@gmail.com> References: <4EE675A8.3030609@niemail.de> <4EE71663.5040308@gmail.com> <4EE72A94.6040904@gmail.com> <4EE75080.1000909@citrix.com> <1323783428.20077.298.camel@zakaz.uk.xensource.com> <4EE7BC9B.6040003@gmail.com> <1323815427.20936.96.camel@dagon.hellion.org.uk> <4EE7D75B.6080209@gmail.com> <1323847523.20936.110.camel@dagon.hellion.org.uk> <1323864969.20077.405.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1323864969.20077.405.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "sandr8@gmail.com" , "xen-devel@lists.xensource.com" , David Vrabel , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 14.12.2011 16:16, Ian Campbell wrote: > I take it back, there is indeed a bug in the PV ops kernel in this > regard. > > It works with xm/xend because they set the maximum reservation for > guests to static-max on boot. xl (and, I think, xapi) instead set the > maximum reservation to the current balloon target and change it > dynamically as the target is changed (as a method of enforcing the > targets). However the pvops kernel incorrectly uses the maximum > reservation at boot to size the physical address space for guests. > > The patch below fixes this. > > (skip) I've checked this patch against current vanilla v3.2-rc5 - it fix problem I wrote about. Is any chance that fix will go to release of 3.2?