From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 1/1] xc_domain_restore: Allow QEMU to increase memory Date: Wed, 15 Apr 2015 15:32:58 +0100 Message-ID: <1429108378.15516.302.camel@citrix.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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <552CE112.40100@cn.fujitsu.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: Hongyang Yang Cc: Wei Liu , Stefano Stabellini , Andrew Cooper , Ian Jackson , Don Slutz , "xen-devel@lists.xen.org" , Shriram Rajagopalan List-Id: xen-devel@lists.xenproject.org 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. Ian.