From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] allow xm2xl migration for xen-4.3 Date: Wed, 30 Apr 2014 10:41:50 +0200 Message-ID: <20140430084150.GA32418@aepfle.de> References: <1398701590.29700.172.camel@kazak.uk.xensource.com> <1398790633-7503-1-git-send-email-v.tolstov@selfip.ru> <1398846405.27484.7.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1398846405.27484.7.camel@kazak.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: Ian Campbell Cc: xen-devel@lists.xensource.com, v.tolstov@selfip.ru List-Id: xen-devel@lists.xenproject.org On Wed, Apr 30, Ian Campbell wrote: > On Tue, 2014-04-29 at 20:57 +0400, v.tolstov@selfip.ru wrote: > > From: Vasiliy Tolstov > > Thanks. Which tree does this apply to and how would I go about using it? > > I think it applies to xen 4.3 and is supposed to allow a guest started > by xm to be migrated with xl, to create an xl compatible vm, is that > correct? If not can you give the method for using it please. Does that migrate from qemu-xen-traditional to qemu-xen? And if so, is that supposed to work anyway? I think the right approach would be to start the remote side with device_model=qemu-xen-traditional. Olaf