From mboxrd@z Thu Jan  1 00:00:00 1970
From: Don Slutz <dslutz@verizon.com>
Subject: Re: [PATCH 1/1] xc_domain_restore: Allow QEMU to
 increase memory
Date: Wed, 15 Apr 2015 14:24:36 -0400
Message-ID: <552EACE4.4080909@one.verizon.com>
References: <552CD5A7.4080803@citrix.com> <552CDC57.1020107@cn.fujitsu.com>
	<20150414092937.GO17670@zion.uk.xensource.com>
	<552CE088.1060401@cn.fujitsu.com>
	<20150414095221.GR17670@zion.uk.xensource.com>
	<552D51CA.9040209@one.verizon.com>
	<20150414175437.GB11717@zion.uk.xensource.com>
	<1429108488.15516.303.camel@citrix.com>
	<20150415163612.GB29894@zion.uk.xensource.com>
	<1429116315.25195.24.camel@citrix.com>
	<20150415165231.GD29894@zion.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20150415165231.GD29894@zion.uk.xensource.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: Wei Liu <wei.liu2@citrix.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, George Dunlap <george.dunlap@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Shriram Rajagopalan <rshriram@cs.ubc.ca>, Hongyang Yang <yanghy@cn.fujitsu.com>
List-Id: xen-devel@lists.xenproject.org

On 04/15/15 12:52, Wei Liu wrote:
> On Wed, Apr 15, 2015 at 05:45:15PM +0100, Ian Campbell wrote:
>> On Wed, 2015-04-15 at 17:36 +0100, Wei Liu wrote:
>>> On Wed, Apr 15, 2015 at 03:34:48PM +0100, Ian Campbell wrote:
>>>> On Tue, 2015-04-14 at 18:54 +0100, Wei Liu wrote:
>>>>> Let's see if we can record this in xc image format. I haven't looked,
>>>>> but George mentioned that it might be possible to do so.
>>>>
>>>> Can this not be done at the save stage in the bit where we update the
>>>> JSON to reflect the actual configuration?
>>>>
>>>
>>> Yes, it's possible to do that. The value is not in libxl idl simply
>>> because it's always not there.
>>
>> We can't set the existing maxmem then?
>>
> 
> If the "we" in your question means an applications that use libxl's
> public interface, then no. It's not in IDL. It's not in xenstore. That
> value is currently managed by libxl + libxc + xen.
> 

And just to be clear all this is related to LIBXL_MAXMEM_CONSTANT.
Which is not in JSON, nor xenstore, nor libxc, nor xen.

   -Don Slutz

> Wei.
> 
>>> But this might not help COLO / Remus.  If they don't use that API to
>>> retrieve domain configuration, a stale value might still get sent to the
>>> other end.
>>>
>>> Wei.
>>>
>>>> Ian.
>>