From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vasiliy G Tolstov Subject: RE: RE: "xm create" take more time to return. Date: Thu, 25 Nov 2010 15:13:08 +0300 Message-ID: <1290687188.25657.2.camel@vase> References: <749B9D3DBF0F054390025D9EAFF47F223023AB34@shsmsx501.ccr.corp.intel.com> <749B9D3DBF0F054390025D9EAFF47F223029883B@shsmsx501.ccr.corp.intel.com> Reply-To: v.tolstov@selfip.ru Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: "Zhang, Yang Z" , Keir Fraser , "xen-devel@lists.xensource.com" , Ian Jackson List-Id: xen-devel@lists.xenproject.org On Thu, 2010-11-25 at 10:48 +0000, Stefano Stabellini wrote: > On Thu, 25 Nov 2010, Zhang, Yang Z wrote: > > Hi keir > > Our testing is base on xm now . And we know xl will be official supported by xen 4.1, so should we move to xl now or after xen 4.1 release? > > > > I think it makes sense to start now, considering that on January > xen-unstable is going to freeze anyway. > If you don't use python in your VM config files it should be just a > matter of linking xl to xm. > > > > BTW: we had investigated xl several months ago, and there were some problems with it(I have send a mail to discuss it before), but I am not sure whether those bugs are fixed or not. > > > > We'll try to fix any issues that you might find. > Can You try to fix xm issues too (only this). I hope that novell team moved from xm to xl in thair sles rpms.... -- Vasiliy G Tolstov Selfip.Ru