From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: xl mem-max error Date: Mon, 10 Nov 2014 12:44:07 +0000 Message-ID: <1415623447.25176.12.camel@citrix.com> References: <545BF386.1050106@oracle.com> <20141107110512.GA12109@zion.uk.xensource.com> <545CD572.9040801@oracle.com> <20141110123747.GE28360@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XnoKP-0003Rq-7H for xen-devel@lists.xenproject.org; Mon, 10 Nov 2014 12:44:17 +0000 In-Reply-To: <20141110123747.GE28360@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: xen-devel , Zhigang Wang , Ian Jackson List-Id: xen-devel@lists.xenproject.org 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? Ian.