Re: [Xen-devel] xm mem-set issues

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 11 May 2006, at 22:26, Puthiyaparambil, Aravindh wrote:

> > The bug here is that 'xm list' shows the current target allocation for
> > the guest (as specified to mem-set) rather than what the guest is
> > currently using. It'd be good to fix this.
> I thought the balloon driver was going through with the increase. I 
> will
> send in a fix for this too.
It'll go as far as it can, subject to its reservation cap and subject 
to physical memory limitations of the host system. The balloon driver 
and the memory targetting system are working okay here I think.
> And for the mem-set to less that 2% of initial memory issue, I am
> assuming the check should go in the balloon driver. Am I right?
That would probably be a good idea. I'd prefer a more dynamic check 
that hooked off Linux low-memory paths (e.g., steps in before the OOM 
killer) and got the balloon driver to back off. That would work in a 
wider range of situations.
 -- Keir


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