From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: qemu devel <qemu-devel@nongnu.org>, Eric Blake <eblake@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
Bian Naimeng <biannm@cn.fujitsu.com>,
"eddie . dong" <eddie.dong@intel.com>
Subject: [Qemu-devel] [PATCH V6 0/2] Add new qmp commands to suppurt Xen COLO
Date: Thu, 5 Jan 2017 14:08:50 +0800 [thread overview]
Message-ID: <1483596532-14552-1-git-send-email-zhangchen.fnst@cn.fujitsu.com> (raw)
Xen COLO depend on qemu COLO replication function.
So, We need new qmp commands for Xen to use qemu replication.
Corresponding libxl patches already in xen.git.
Commit ID:
ed37ef1f91c20f0ab162ce60f8c38400b917fa64
COLO: introduce new API to prepare/start/do/get_error/stop replication
a0ddc0b359375b2418213966dfbdbfab593ecc6f
tools/libxl: introduction of libxl__qmp_restore to load qemu state
Zhang Chen (2):
Add a new qmp command to start/stop replication
Add a new qmp command to do checkpoint, query xen replication status
docs/qmp-commands.txt | 42 +++++++++++++++++++++++++++++++
migration/colo.c | 40 +++++++++++++++++++++++++++++
qapi-schema.json | 69 +++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 151 insertions(+)
--
2.7.4
next reply other threads:[~2017-01-05 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 6:08 Zhang Chen [this message]
2017-01-05 6:08 ` [Qemu-devel] [PATCH V6 1/2] Add a new qmp command to start/stop replication Zhang Chen
2017-01-05 6:08 ` [Qemu-devel] [PATCH V6 2/2] Add a new qmp command to do checkpoint, query xen replication status Zhang Chen
2017-02-07 15:50 ` Eric Blake
2017-02-08 2:22 ` Zhang Chen
2017-01-19 9:57 ` [Qemu-devel] [PATCH V6 0/2] Add new qmp commands to suppurt Xen COLO Zhang Chen
2017-01-26 3:04 ` Zhang Chen
2017-01-26 3:10 ` Jason Wang
2017-02-06 13:13 ` Dr. David Alan Gilbert
2017-02-07 2:01 ` Zhang Chen
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=1483596532-14552-1-git-send-email-zhangchen.fnst@cn.fujitsu.com \
--to=zhangchen.fnst@cn.fujitsu.com \
--cc=biannm@cn.fujitsu.com \
--cc=eblake@redhat.com \
--cc=eddie.dong@intel.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.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).