From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Shuklin Subject: Re: a ton of kernel issues Date: Wed, 14 Dec 2011 00:59:07 +0400 Message-ID: <4EE7BC9B.6040003@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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1323783428.20077.298.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: "xen-devel@lists.xensource.com" , David Vrabel , "sandr8@gmail.com" List-Id: xen-devel@lists.xenproject.org On 13.12.2011 17:37, Ian Campbell wrote: >> This should work if memory hotplug is enabled. >> >> It is also supported without memory hotplug but this requires that the >> tools supply a suitable memory map that covers the largest >> memory-static-max limit you wish to support. I'm not sure if the tools >> can do this yet. > With xl this should work using the "maxmem" option. (xm probably uses > the same name) > I'm not sure what maxmem do, but I can say, this option does not allow to go beyond initial boot memory for pv_ops kernels and beyond static-max memory for -xen kernel. I tested it with following python script (under xcp, with shutdowned squeezed to be sure not get 'reballanced'): xc.domain_setmaxmem(domid,memory) xs.write("","/local/domain/%i/memory/dynamic-min"%domid,str(memory*1024)) xs.write("","/local/domain/%i/memory/dynamic-max"%domid,str(memory*1024)) xs.write("","/local/domain/%i/memory/static-max"%domid,str(memory*1024)) xs.write("","/local/domain/%i/memory/target"%domid,str(memory*1024)) It works fine within noted ranges, but simply ignores any request higher them.