From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Wilson Subject: Re: Support for xm create -F (sxp configuration files) Date: Mon, 16 Sep 2013 09:49:52 -0700 Message-ID: <20130916164922.GA22280@u109add4315675089e695.ant.amazon.com> References: <1377906042-12816-1-git-send-email-msw@linux.com> <20130902203256.GA23391@u109add4315675089e695.ant.amazon.com> <1378979449.10076.28.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VLbzr-00080O-Mr for xen-devel@lists.xenproject.org; Mon, 16 Sep 2013 16:49:59 +0000 Received: by mail-yh0-f45.google.com with SMTP id i72so2156343yha.32 for ; Mon, 16 Sep 2013 09:49:57 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1378979449.10076.28.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: Steven Noonan , Stefano Stabellini , George Dunlap , Ian Jackson , Matt Wilson , xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Sep 12, 2013 at 10:50:49AM +0100, Ian Campbell wrote: > create ! > title it xl lacks support for xm create -F (sxp config file syntax) > > On Mon, 2013-09-02 at 13:32 -0700, Matt Wilson wrote: > > > > Live migration between a system running xend to a system that doesn't > > support xend would be a nice-to-have. That probably means some support > > for SXP parsing either in libxl or in some compatibility tool. > > Matt mentioned elsewhere that they use "xm create -F" which takes a > configuration file in the xend sxp format (I had no idea this option > existed). > > I don't think we really want to be adding SXP code to xm but perhaps we > can produce a conversion tool? Indeed, also mentioned elsewhere it's probably not in the best interest of the project to go adding SXP support when we already have more well adopted options like json. > Matt, can you provide some examples of the actual SXP you care about, we > obviously don't want to be worrying about the bits which aren't actually > used. Honestly I think it'd be less total work to avoid SXP altogether. There are some other differences that need to be carefully considered, and shifting config file formats is a forcing function for looking closely for those differences. --msw