Re: [Xen-devel] a ton of kernel issues

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2011-12-13 at 20:59 +0000, George Shuklin wrote:
> 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

maxmem sets static-max for the guest in the xl toolstack.

> 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.

AFAIK the toolstack support for memory hotplug (i.e. growing beyond
static-max) does not yet exist.

> 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.

If you are stepping outside the toolstack and doing this sort of thing
behind its back then all bets are off and you can't really expect people
here to help you.

Please try and reproduce the issue using the standard toolstack options.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel