From: Alex Bligh <alex@alex.org.uk>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Alex Bligh <alex@alex.org.uk>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [RFC] Enabling live-migrate on HVM on qemu-xen device model
Date: Thu, 13 Dec 2012 11:03:07 +0000 [thread overview]
Message-ID: <FBCCA7FECCCD18AFDA45C114@nimrod.local> (raw)
In-Reply-To: <1355396228-3183-1-git-send-email-alex@alex.org.uk>
Apologies, I missed the vital information that this is a patch for Xen-4.2,
against current xen-4.2-testing.
--On 13 December 2012 10:56:58 +0000 Alex Bligh <alex@alex.org.uk> wrote:
> This is a COMPILE TESTED ONLY RFC for a backport of the libxl elements
> of:
>
> http://marc.info/?l=xen-devel&m=134944750724252
>
> Stefano Stabellini said he would look at backporting the qemu-xen
> side.
>
> My first question is whether this is the right approach: do we want
> to include the JSON changes too (presumably it changes the API).
> I am not 100% convinced they are necessary to get live migrate
> working.
>
> DO NOT RUN THIS CODE ON ANYTHING YOU CARE ABOUT.
>
>
--
Alex Bligh
next prev parent reply other threads:[~2012-12-13 11:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 11:45 Xen 4.2.1 live migration with qemu device model Alex Bligh
2012-12-11 12:05 ` Alex Bligh
2012-12-11 14:12 ` Ian Campbell
2012-12-12 16:45 ` Ian Jackson
2012-12-13 11:46 ` Ian Campbell
2012-12-11 14:09 ` Ian Campbell
2012-12-11 15:07 ` Alex Bligh
2012-12-11 15:11 ` Ian Campbell
2012-12-11 15:26 ` Stefano Stabellini
2012-12-11 19:14 ` Alex Bligh
2012-12-11 19:24 ` Stefano Stabellini
2012-12-11 19:51 ` Alex Bligh
2012-12-12 13:04 ` QEMU qcow2 snapshotting (was Xen 4.2.1 live migration with qemu device model) Stefano Stabellini
2012-12-12 15:22 ` Alex Bligh
2012-12-13 10:56 ` [RFC] Enabling live-migrate on HVM on qemu-xen device model Alex Bligh
2012-12-13 10:56 ` [PATCH 01/10] libxl_json: Export json_object related function Alex Bligh
2012-12-13 10:57 ` [PATCH 02/10] libxl_json: Remove JSON_ERROR from enum Alex Bligh
2012-12-13 10:57 ` [PATCH 03/10] libxl_json: Replace JSON_TRUE/FALSE by JSON_BOOL Alex Bligh
2012-12-13 10:57 ` [PATCH 04/10] libxl_json: Introduce libxl__json_object_to_yajl_gen Alex Bligh
2012-12-13 10:57 ` [PATCH 05/10] libxl_qmp: Introduces helpers to create an argument list Alex Bligh
2012-12-13 10:57 ` [PATCH 06/10] libxl_qmp: Use qmp_parameters_* functions for param list of a QMP command Alex Bligh
2012-12-13 10:57 ` [PATCH 07/10] libxl_qmp: Simplify run of single QMP commands Alex Bligh
2012-12-13 10:57 ` [PATCH 08/10] libxl_qmp: Introduce libxl__qmp_set_global_dirty_log Alex Bligh
2012-12-13 10:57 ` [PATCH 09/10] libxl_dom: Call the right switch logdirty for the right DM Alex Bligh
2012-12-13 10:57 ` [PATCH 10/10] libxl: Allow migration with qemu-xen Alex Bligh
2012-12-13 11:03 ` Alex Bligh [this message]
2012-12-13 11:38 ` [RFC] Enabling live-migrate on HVM on qemu-xen device model Ian Campbell
2012-12-13 15:06 ` Alex Bligh
2012-12-13 15:09 ` Ian Jackson
2012-12-17 12:01 ` Ian Campbell
2012-12-17 17:02 ` Alex Bligh
2012-12-18 10:04 ` Ian Campbell
2012-12-18 11:04 ` George Dunlap
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=FBCCA7FECCCD18AFDA45C114@nimrod.local \
--to=alex@alex.org.uk \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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).