From: Ian Campbell <Ian.Campbell@citrix.com>
To: Matt Wilson <msw@linux.com>
Cc: Steven Noonan <snoonan@amazon.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Matt Wilson <msw@amazon.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: xend deprecation
Date: Wed, 4 Sep 2013 08:29:07 +0100 [thread overview]
Message-ID: <1378279747.6935.22.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20130904060642.GB25227@u109add4315675089e695.ant.amazon.com>
On Tue, 2013-09-03 at 23:06 -0700, Matt Wilson wrote:
> On Tue, Sep 03, 2013 at 09:03:46AM +0100, Ian Campbell wrote:
> > 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.
> >
> > This already works by using xl on the source side, e.g. a guest started
> > with xend on 4.1 can be migrated with 4.1's xl to 4.2.
> >
> > http://lists.xen.org/archives/html/xen-devel/2012-08/msg02191.html
>
> xl doesn't run everywhere that we need it to.
Details please, or we aren't going to be able to even think about how to
solve this for you.
BTW You can also do a xend migration to e.g. 4.2 (using the xend whichis
in 4.2) and the use 4.2's xl to do a localhost migrate or a second
remote migrate to another 4.2 system.
xend's deprecation has been on the cards, and widely known, for several
releases now. It is time to quit stalling and start moving. I intend to
post a patch deleting it as soon as 4.4 is out the door.
Of course you are also free to pick up xend maintenance if you really
want to keep it alive. We could for example move it out of tree. And by
"We" I mean "You and those others who are interested in continuing with
xend".
Ian.
next prev parent reply other threads:[~2013-09-04 7:29 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 23:40 [PATCH] xend: handle extended PCI configuration space when saving state Matt Wilson
2013-09-02 9:53 ` George Dunlap
2013-09-02 20:32 ` xend deprecation [Was: Re: [PATCH] xend: handle extended PCI configuration space when saving state] Matt Wilson
2013-09-03 8:03 ` Ian Campbell
2013-09-04 6:06 ` xend deprecation Matt Wilson
2013-09-04 7:29 ` Ian Campbell [this message]
2013-09-04 14:04 ` Konrad Rzeszutek Wilk
2013-09-04 15:18 ` George Dunlap
2013-09-04 15:34 ` Ian Campbell
2013-09-04 15:43 ` Ian Jackson
2013-09-12 10:02 ` Ian Campbell
2013-09-12 10:15 ` Processed: " xen
2013-09-12 11:10 ` Ian Jackson
2013-09-04 15:49 ` Tim Deegan
2013-09-04 16:17 ` Ian Jackson
2013-09-04 16:24 ` Ian Campbell
2013-09-04 16:33 ` Konrad Rzeszutek Wilk
2013-09-05 9:12 ` George Dunlap
2013-09-06 13:36 ` Konrad Rzeszutek Wilk
2013-09-06 13:49 ` Ian Campbell
2013-09-06 14:01 ` Jan Beulich
2013-09-06 14:15 ` Ian Campbell
2013-09-05 10:18 ` Fabio Fantoni
2013-09-05 10:27 ` George Dunlap
2013-09-05 10:46 ` George Dunlap
2013-09-04 16:29 ` Konrad Rzeszutek Wilk
2013-09-12 12:52 ` [PATCH] xl: print runtime info in "xl list -l" Ian Campbell
2013-09-25 17:41 ` Konrad Rzeszutek Wilk
2013-09-25 17:56 ` Ian Campbell
2013-09-25 18:25 ` Konrad Rzeszutek Wilk
2013-09-25 17:59 ` Ian Campbell
2013-09-25 18:27 ` Konrad Rzeszutek Wilk
2013-10-28 15:51 ` Wei Liu
2013-09-12 14:02 ` xend deprecation Ian Campbell
2013-10-21 14:09 ` Wei Liu
2013-10-21 15:13 ` Zhigang Wang
2013-10-21 15:33 ` Ian Campbell
2013-10-21 15:35 ` Ian Campbell
2013-09-04 12:57 ` Stefano Stabellini
2013-09-12 9:50 ` Support for xm create -F (sxp configuration files) Ian Campbell
2013-09-12 10:00 ` Processed: " xen
2013-09-16 16:49 ` Matt Wilson
2013-11-05 14:39 ` Ian Campbell
2013-11-05 14:45 ` Processed: " xen
2013-09-03 16:33 ` [PATCH] xend: handle extended PCI configuration space when saving state Ian Campbell
2013-09-04 6:12 ` Matt Wilson
2013-09-04 6:47 ` Noonan, Steven
2013-09-04 7:30 ` Ian Campbell
2013-09-04 10:14 ` Ian Jackson
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=1378279747.6935.22.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=msw@amazon.com \
--cc=msw@linux.com \
--cc=snoonan@amazon.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).