From: Vasiliy G Tolstov <v.tolstov@selfip.ru>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
Keir Fraser <keir@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: RE: RE: "xm create" take more time to return.
Date: Thu, 25 Nov 2010 15:13:08 +0300 [thread overview]
Message-ID: <1290687188.25657.2.camel@vase> (raw)
In-Reply-To: <alpine.DEB.2.00.1011251046290.2373@kaball-desktop>
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 <v.tolstov@selfip.ru>
Selfip.Ru
next prev parent reply other threads:[~2010-11-25 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 1:47 "xm create" take more time to return Zhang, Yang Z
2010-11-24 3:14 ` Zhang, Yang Z
2010-11-24 9:02 ` Keir Fraser
2010-11-24 9:04 ` Zhang, Yang Z
2010-11-25 7:38 ` Zhang, Yang Z
2010-11-25 10:48 ` Stefano Stabellini
2010-11-25 12:13 ` Vasiliy G Tolstov [this message]
2010-11-30 1:40 ` Zhang, Yang Z
2010-11-30 2:50 ` Zhang, Yang Z
2010-11-24 12:18 ` Vasiliy G Tolstov
2010-11-24 12:23 ` Stefano Stabellini
2010-11-24 12:26 ` Vasiliy G Tolstov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1290687188.25657.2.camel@vase \
--to=v.tolstov@selfip.ru \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.