From: "Vincent, Pradeep" <pradeepv@amazon.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Dulloor <dulloor@gmail.com>
Subject: Re: New feature support - xl or xm ?
Date: Mon, 7 Jun 2010 18:35:46 -0700 [thread overview]
Message-ID: <C832EC82.17AB4%pradeepv@amazon.com> (raw)
In-Reply-To: <19460.57088.748052.808033@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1352 bytes --]
I haven't looked deeply into 'xl' but..
>From the recent Xen summit, I walked away thinking 'xl' didn't have the callback mechanisms (e.g. Cleanup etc) and this helped it stay stateless while falling short of full 'xm' replacement. This email thread indicates 'xm/xend' will be deprecated in due course of time. Did I miss anything here ?
Is migration of VMs from 'xm' managed hosts to 'xl' managed hosts expected to work ?
I think moving away from commonly used xend/xm could be a bit of a thorn particularly if the 'xm' to 'xl' migration isn't expected to work.
Thoughts ?
Thanks,
- Pradeep Vincent
On 6/1/10 3:20 AM, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
Stefano Stabellini writes ("Re: [Xen-devel] New feature support - xl or xm ?"):
> On Fri, 28 May 2010, Dulloor wrote:
> > If we are to add new guest configuration parameters, is it enough to
> > make it work with xl ?
> > Sorry, if I missed any past mails regarding this, but (in general)
> > should people think xl or xm or both ?
>
> xl is strongly recommended at this point.
Indeed. I think at this point it's probably OK to submit features for
libxl only and not add them to xm/xend too.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2094 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-06-08 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 22:37 New feature support - xl or xm ? Dulloor
2010-05-28 22:41 ` Stefano Stabellini
2010-06-01 10:20 ` Ian Jackson
2010-06-08 1:35 ` Vincent, Pradeep [this message]
2010-06-08 9:17 ` Stefano Stabellini
2010-06-08 22:49 ` Vincent, Pradeep
2010-06-08 23:37 ` Vincent, Pradeep
2010-06-09 15:09 ` Stefano Stabellini
2010-06-09 17:30 ` Vincent, Pradeep
2010-06-10 20:02 ` AP Xen
2010-06-10 20:19 ` Keir Fraser
2010-06-09 14:43 ` Stefano Stabellini
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=C832EC82.17AB4%pradeepv@amazon.com \
--to=pradeepv@amazon.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dulloor@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.