Re: [PATCH 1/1] xc_domain_restore: Allow QEMU to increase memory

[Don Slutz <dslutz@verizon.com>]

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.
>