From: George Shuklin <george.shuklin@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>,
"sandr8@gmail.com" <sandr8@gmail.com>
Subject: Re: a ton of kernel issues
Date: Wed, 14 Dec 2011 00:59:07 +0400 [thread overview]
Message-ID: <4EE7BC9B.6040003@gmail.com> (raw)
In-Reply-To: <1323783428.20077.298.camel@zakaz.uk.xensource.com>
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.
next prev parent reply other threads:[~2011-12-13 20:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 21:44 a ton of kernel issues Tim Evers
2011-12-12 21:56 ` Konrad Rzeszutek Wilk
2011-12-14 9:00 ` Tim Evers
2011-12-15 1:25 ` Konrad Rzeszutek Wilk
2011-12-13 9:09 ` George Shuklin
2011-12-13 10:19 ` Alessandro Salvatori
2011-12-13 10:36 ` George Shuklin
2011-12-13 13:17 ` David Vrabel
2011-12-13 13:37 ` Ian Campbell
2011-12-13 20:59 ` George Shuklin [this message]
2011-12-13 22:30 ` Ian Campbell
2011-12-13 22:53 ` George Shuklin
2011-12-14 7:25 ` Ian Campbell
2011-12-14 12:16 ` Ian Campbell
2011-12-14 12:21 ` David Vrabel
2011-12-14 13:11 ` Jan Beulich
2011-12-14 13:48 ` Ian Campbell
2011-12-14 17:44 ` Konrad Rzeszutek Wilk
2011-12-15 12:45 ` George Shuklin
2011-12-15 16:26 ` Konrad Rzeszutek Wilk
2011-12-13 21:05 ` George Shuklin
2011-12-13 21:45 ` Konrad Rzeszutek Wilk
2011-12-14 12:28 ` David Vrabel
2011-12-14 16:57 ` Konrad Rzeszutek Wilk
2011-12-14 7:47 ` Fajar A. Nugraha
2011-12-14 18:40 ` George Shuklin
2011-12-13 14:18 ` Konrad Rzeszutek Wilk
2011-12-13 21:10 ` George Shuklin
2011-12-13 21:38 ` Konrad Rzeszutek Wilk
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=4EE7BC9B.6040003@gmail.com \
--to=george.shuklin@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=sandr8@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.