[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2/2] libxl: xl mem-set should not enforce memory limits

On Fri, Mar 15, 2013 at 04:32:53PM +0000, Ian Campbell wrote:
> On Fri, 2013-03-15 at 16:25 +0000, Daniel Kiper wrote:
> > xl mem-set should not enforce memory limits. If it does
> NB the title says libxl but this is actually an xl change.


> > then after decreasing reservation there is no chance to
> > increase reservation directly from guest domain by
> > writing to /sys/devices/system/xen_memory/xen_memory0/target*
> This is a feature not a bug I think. It is intentional that if the host
> admin sets a memory target the a guest admin cannot exceed that limit.

I think that xl mem-max should be used to enforce limits. If admin
would like to enforce "hard" limit it should call xl mem-set and
xl mem-max in sequence. If we would like to leave old xl mem-set
behavior we should change comment for this command because now
it does not mention anythig about limit enforcement. Or we should
add an option which explicitly disables memory limit enforment
(this behavior is in line with xm mem-set behavior).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.