From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xl mem-max error
Date: Mon, 10 Nov 2014 15:30:35 +0000
Message-ID: <1415633435.25176.27.camel@citrix.com>
References: <545BF386.1050106@oracle.com>
	<20141107110512.GA12109@zion.uk.xensource.com>
	<545CD572.9040801@oracle.com>
	<20141110123747.GE28360@zion.uk.xensource.com>
	<1415623447.25176.12.camel@citrix.com> <5460D9C5.4020905@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1XnqvU-0001AA-M5
	for xen-devel@lists.xenproject.org; Mon, 10 Nov 2014 15:30:44 +0000
In-Reply-To: <5460D9C5.4020905@oracle.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Zhigang Wang <zhigang.x.wang@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Wei Liu <wei.liu2@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

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