From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 17/27] tools/libxl: Support converting a legacy stream to a v2 stream Date: Tue, 16 Jun 2015 16:38:24 +0100 Message-ID: <1434469104.13744.236.camel@citrix.com> References: <1434375880-30914-1-git-send-email-andrew.cooper3@citrix.com> <1434375880-30914-18-git-send-email-andrew.cooper3@citrix.com> <1434465530.13744.199.camel@citrix.com> <55803CFD.6060202@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55803CFD.6060202@citrix.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: Andrew Cooper Cc: Wei Liu , Yang Hongyang , Ian Jackson , Xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, 2015-06-16 at 16:13 +0100, Andrew Cooper wrote: > > Since we only support N->N+1 we could perhaps tolerate the duplication > > if we agreed upon a reasonable schedule to remove all this compat stuff, > > e.g. in 4.7 or 4.8. > > N->N+1 is another item on the "needs to be resolved before Xapi can use > libxl" list. > > In XenServer, we still have support for importing VMs from XenServer > 4.0, which is certainly older than Xen 3.2 OK. FWIW I think we should consider importing (i.e. restore) separate to migration, since the former can be subjected to more heavy duty offline conversions if necessary. It's not out of the question that this new migration stream format will allow us to sensibly increase the +1 to some larger number for migrations too. Ian. > It might be reasonable to make a compile time option to omit the legacy > conversion, but conversion should absolutely be on by default for the > first release after this series being accepted. > > ~Andrew