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 16:41:54 -0400
Message-ID: <552ECD12.3040704@one.verizon.com>
References: <1428941353-18673-1-git-send-email-dslutz@verizon.com>	
	<552BEDF1.7070209@citrix.com> <552C5683.1040903@one.verizon.com>	
	<552CD5A7.4080803@citrix.com> <552CDC57.1020107@cn.fujitsu.com>	
	<552CDDDB.5050806@citrix.com> <552CE112.40100@cn.fujitsu.com>
	<1429108378.15516.302.camel@citrix.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: <1429108378.15516.302.camel@citrix.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: Ian Campbell <ian.campbell@citrix.com>, Hongyang Yang <yanghy@cn.fujitsu.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Stefano Stabellini <stefano.stabellini@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>
List-Id: xen-devel@lists.xenproject.org

On 04/15/15 10:32, Ian Campbell wrote:
> On Tue, 2015-04-14 at 17:42 +0800, Hongyang Yang wrote:
>>
>> On 04/14/2015 05:28 PM, Andrew Cooper wrote:
> 
>>> Funny you should ask that.  Migrationv2 for libxl moves the JSON config
>>> blob into the libxl stream, rather than being a singleshot action at the
>>> very start.  From that point, it becomes plausible to send a new JSON
>>> blob when an update on the source side occurs.
>>
>> That should solve the problem, but Migrationv2 for libxl won't be in upstream
>> for the moment, the bug still exists, is there a way to solve the problem
>> now under v1 migration?
> 
> As far as I am concerned migration v2 is a prerequisite for COLO. We
> won't be taking any major changes to the v1 code at this point.
> 

So is:

Date: Tue, 14 Apr 2015 18:06:26 -0400
Subject: [PATCH v2 1/1] tools: Handle xc_maxmem adjustments
Thread-Topic: [PATCH v2 1/1] tools: Handle xc_maxmem adjustments
Thread-Index: AdB2/0pJoAZieMWqTomVEBNbV7iiEA==
Message-ID: <1429049186-27343-1-git-send-email-dslutz@verizon.com>
References: <20150414175437.GB11717@zion.uk.xensource.com>
In-Reply-To: <20150414175437.GB11717@zion.uk.xensource.com>

a major change to the v1 code?

   -Don Slutz


> Ian.
>