Re: [Xen-devel] xl mem-max error

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2014-11-10 at 10:29 -0500, Zhigang Wang wrote:
> On 11/10/2014 07:44 AM, Ian Campbell wrote:
> > On Mon, 2014-11-10 at 12:37 +0000, Wei Liu wrote:
> > 
> >> Ian and Ian, any thought how this bug came into being? I think we should
> >> fix this for 4.5, but I don't think I know enough of how memory target
> >> is expected to behave.
> >>
> > 
> > I'm confused by the description of what's going on, in particular the
> > mixing of mem-max commands and target xenstore nodes (since the former
> > doesn't really affect the latter).
> > 
> > How was the domain started (memory= and maxmem=).
> > 
> > What were static-max and target at the point?
> > 
> > What did they change to when xl mem-max was issued? 
> > 
> > What did you expect them to change to instead?
> 
> Sorry for the confusion I made. Here is the problem I encountered:

This is just restating what was upthread, which, as I say, is confusing
to me.

Please can you just answer the 4 questions I asked and we can take it
from there.

> 
> 1. Start a VM with 'memory = 700'.
> 2. Doing 'xl mem-max <domid> 700' will cause a error.
> 
> My expectation: after I start a VM with 'memory = 700', I can do 'xl mem-max 
> <domid> 700'.
> 
> A little analysis of the problem:
> 
> 1. Error: "libxl: error: libxl.c:4549:libxl_domain_setmaxmem: 
> memory_static_max must be greater than or or equal to memory_dynamic_max"
> 
> 2. I find static-max always less then target memory in xenstore:
> 
>     /local/domain/3/memory/static-max = "716800" (memory_static_max)
>     /local/domain/3/memory/target = "716801"     (memory_dynamic_max)
> 
>    which looks bogus.
> 
> Thanks,
> 
> Zhigang



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel