From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Yang Hongyang <yanghy@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, eddie.dong@intel.com,
GuiJianfeng@cn.fujitsu.com, mrhines@linux.vnet.ibm.com,
wency@cn.fujitsu.com
Subject: Re: [RFC PATCH 00/17] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service
Date: Fri, 1 Aug 2014 17:02:42 +0100 [thread overview]
Message-ID: <20140801160242.GI2430@work-vm> (raw)
In-Reply-To: <1406125538-27992-1-git-send-email-yanghy@cn.fujitsu.com>
* Yang Hongyang (yanghy@cn.fujitsu.com) wrote:
> Virtual machine (VM) replication is a well known technique for
> providing application-agnostic software-implemented hardware fault
> tolerance "non-stop service". COLO is a high availability solution.
> Both primary VM (PVM) and secondary VM (SVM) run in parallel. They
> receive the same request from client, and generate response in parallel
> too. If the response packets from PVM and SVM are identical, they are
> released immediately. Otherwise, a VM checkpoint (on demand) is
> conducted. The idea is presented in Xen summit 2012, and 2013,
> and academia paper in SOCC 2013. It's also presented in KVM forum
> 2013:
> http://www.linux-kvm.org/wiki/images/1/1d/Kvm-forum-2013-COLO.pdf
> Please refer to above document for detailed information.
> Please also refer to previous posted RFC proposal:
> http://lists.nongnu.org/archive/html/qemu-devel/2014-06/msg05567.html
Hi Yang,
Thanks for this set of patches (and I've replied to many individually).
> The patchset is also hosted on github:
> https://github.com/macrosheep/qemu/tree/colo_v0.1
>
> This patchset is RFC, implements the frame of colo, without
> failover and nic/disk replication. But it is ready for demo
> the COLO idea above QEMU-Kvm.
> Steps using this patchset to get an overview of COLO:
> 1. configure the source with --enable-colo option
> 2. compile
> 3. just like QEMU's normal migration, run 2 QEMU VM:
> - Primary VM
> - Secondary VM with -incoming tcp:[IP]:[PORT] option
> 4. on Primary VM's QEMU monitor, run following command:
> migrate_set_capability colo on
> migrate tcp:[IP]:[PORT]
> 5. done
> you will see two runing VMs, whenever you make changes to PVM, SVM
> will be synced to PVM's state.
>
> TODO list:
> 1. failover
> 2. nic replication
> 3. disk replication[COLO Disk manager]
I wonder if there are any parts that can be borrowed from other code
to get it going; I notice that the reverse execution patchset
has a network packet record/replay mode:
https://lists.gnu.org/archive/html/qemu-devel/2014-07/msg00157.html
What was used for the nic comparison in the 2013 kvm forum paper?
Dave
>
> Any comments/feedbacks are warmly welcomed.
>
> Thanks,
> Yang
>
> Yang Hongyang (17):
> configure: add CONFIG_COLO to switch COLO support
> COLO: introduce an api colo_supported() to indicate COLO support
> COLO migration: add a migration capability 'colo'
> COLO info: use colo info to tell migration target colo is enabled
> COLO save: integrate COLO checkpointed save into qemu migration
> COLO restore: integrate COLO checkpointed restore into qemu restore
> COLO buffer: implement colo buffer as well as QEMUFileOps based on it
> COLO: disable qdev hotplug
> COLO ctl: implement API's that communicate with colo agent
> COLO ctl: introduce is_slave() and is_master()
> COLO ctl: implement colo checkpoint protocol
> COLO ctl: add a RunState RUN_STATE_COLO
> COLO ctl: implement colo save
> COLO ctl: implement colo restore
> COLO save: reuse migration bitmap under colo checkpoint
> COLO ram cache: implement colo ram cache on slaver
> HACK: trigger checkpoint every 500ms
>
> Makefile.objs | 2 +
> arch_init.c | 174 +++++++++-
> configure | 14 +
> include/exec/cpu-all.h | 1 +
> include/migration/migration-colo.h | 36 +++
> include/migration/migration.h | 13 +
> include/qapi/qmp/qerror.h | 3 +
> migration-colo-comm.c | 78 +++++
> migration-colo.c | 643 +++++++++++++++++++++++++++++++++++++
> migration.c | 45 ++-
> qapi-schema.json | 9 +-
> stubs/Makefile.objs | 1 +
> stubs/migration-colo.c | 34 ++
> vl.c | 12 +
> 14 files changed, 1044 insertions(+), 21 deletions(-)
> create mode 100644 include/migration/migration-colo.h
> create mode 100644 migration-colo-comm.c
> create mode 100644 migration-colo.c
> create mode 100644 stubs/migration-colo.c
>
> --
> 1.9.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
WARNING: multiple messages have this Message-ID (diff)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Yang Hongyang <yanghy@cn.fujitsu.com>
Cc: kvm@vger.kernel.org, GuiJianfeng@cn.fujitsu.com,
eddie.dong@intel.com, qemu-devel@nongnu.org,
mrhines@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH 00/17] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service
Date: Fri, 1 Aug 2014 17:02:42 +0100 [thread overview]
Message-ID: <20140801160242.GI2430@work-vm> (raw)
In-Reply-To: <1406125538-27992-1-git-send-email-yanghy@cn.fujitsu.com>
* Yang Hongyang (yanghy@cn.fujitsu.com) wrote:
> Virtual machine (VM) replication is a well known technique for
> providing application-agnostic software-implemented hardware fault
> tolerance "non-stop service". COLO is a high availability solution.
> Both primary VM (PVM) and secondary VM (SVM) run in parallel. They
> receive the same request from client, and generate response in parallel
> too. If the response packets from PVM and SVM are identical, they are
> released immediately. Otherwise, a VM checkpoint (on demand) is
> conducted. The idea is presented in Xen summit 2012, and 2013,
> and academia paper in SOCC 2013. It's also presented in KVM forum
> 2013:
> http://www.linux-kvm.org/wiki/images/1/1d/Kvm-forum-2013-COLO.pdf
> Please refer to above document for detailed information.
> Please also refer to previous posted RFC proposal:
> http://lists.nongnu.org/archive/html/qemu-devel/2014-06/msg05567.html
Hi Yang,
Thanks for this set of patches (and I've replied to many individually).
> The patchset is also hosted on github:
> https://github.com/macrosheep/qemu/tree/colo_v0.1
>
> This patchset is RFC, implements the frame of colo, without
> failover and nic/disk replication. But it is ready for demo
> the COLO idea above QEMU-Kvm.
> Steps using this patchset to get an overview of COLO:
> 1. configure the source with --enable-colo option
> 2. compile
> 3. just like QEMU's normal migration, run 2 QEMU VM:
> - Primary VM
> - Secondary VM with -incoming tcp:[IP]:[PORT] option
> 4. on Primary VM's QEMU monitor, run following command:
> migrate_set_capability colo on
> migrate tcp:[IP]:[PORT]
> 5. done
> you will see two runing VMs, whenever you make changes to PVM, SVM
> will be synced to PVM's state.
>
> TODO list:
> 1. failover
> 2. nic replication
> 3. disk replication[COLO Disk manager]
I wonder if there are any parts that can be borrowed from other code
to get it going; I notice that the reverse execution patchset
has a network packet record/replay mode:
https://lists.gnu.org/archive/html/qemu-devel/2014-07/msg00157.html
What was used for the nic comparison in the 2013 kvm forum paper?
Dave
>
> Any comments/feedbacks are warmly welcomed.
>
> Thanks,
> Yang
>
> Yang Hongyang (17):
> configure: add CONFIG_COLO to switch COLO support
> COLO: introduce an api colo_supported() to indicate COLO support
> COLO migration: add a migration capability 'colo'
> COLO info: use colo info to tell migration target colo is enabled
> COLO save: integrate COLO checkpointed save into qemu migration
> COLO restore: integrate COLO checkpointed restore into qemu restore
> COLO buffer: implement colo buffer as well as QEMUFileOps based on it
> COLO: disable qdev hotplug
> COLO ctl: implement API's that communicate with colo agent
> COLO ctl: introduce is_slave() and is_master()
> COLO ctl: implement colo checkpoint protocol
> COLO ctl: add a RunState RUN_STATE_COLO
> COLO ctl: implement colo save
> COLO ctl: implement colo restore
> COLO save: reuse migration bitmap under colo checkpoint
> COLO ram cache: implement colo ram cache on slaver
> HACK: trigger checkpoint every 500ms
>
> Makefile.objs | 2 +
> arch_init.c | 174 +++++++++-
> configure | 14 +
> include/exec/cpu-all.h | 1 +
> include/migration/migration-colo.h | 36 +++
> include/migration/migration.h | 13 +
> include/qapi/qmp/qerror.h | 3 +
> migration-colo-comm.c | 78 +++++
> migration-colo.c | 643 +++++++++++++++++++++++++++++++++++++
> migration.c | 45 ++-
> qapi-schema.json | 9 +-
> stubs/Makefile.objs | 1 +
> stubs/migration-colo.c | 34 ++
> vl.c | 12 +
> 14 files changed, 1044 insertions(+), 21 deletions(-)
> create mode 100644 include/migration/migration-colo.h
> create mode 100644 migration-colo-comm.c
> create mode 100644 migration-colo.c
> create mode 100644 stubs/migration-colo.c
>
> --
> 1.9.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-08-01 16:02 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 14:25 [RFC PATCH 00/17] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:25 ` [RFC PATCH 01/17] configure: add CONFIG_COLO to switch COLO support Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:25 ` [RFC PATCH 02/17] COLO: introduce an api colo_supported() to indicate " Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 15:47 ` Eric Blake
2014-07-23 15:47 ` Eric Blake
2014-07-23 14:25 ` [RFC PATCH 03/17] COLO migration: add a migration capability 'colo' Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:41 ` Eric Blake
2014-07-23 14:41 ` Eric Blake
2014-07-23 14:25 ` [RFC PATCH 04/17] COLO info: use colo info to tell migration target colo is enabled Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 14:43 ` Dr. David Alan Gilbert
2014-08-01 14:43 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-09-12 6:36 ` Hongyang Yang
2014-09-12 6:36 ` [Qemu-devel] " Hongyang Yang
2014-07-23 14:25 ` [RFC PATCH 05/17] COLO save: integrate COLO checkpointed save into qemu migration Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 14:46 ` Dr. David Alan Gilbert
2014-08-01 14:46 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-07-23 14:25 ` [RFC PATCH 06/17] COLO restore: integrate COLO checkpointed restore into qemu restore Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:25 ` [RFC PATCH 07/17] COLO buffer: implement colo buffer as well as QEMUFileOps based on it Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 18:24 ` Eric Blake
2014-07-23 18:24 ` Eric Blake
2014-08-01 14:52 ` Dr. David Alan Gilbert
2014-08-01 14:52 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-09-17 1:43 ` Hongyang Yang
2014-09-17 1:43 ` [Qemu-devel] " Hongyang Yang
2014-07-23 14:25 ` [RFC PATCH 08/17] COLO: disable qdev hotplug Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:25 ` [RFC PATCH 09/17] COLO ctl: implement API's that communicate with colo agent Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:25 ` [RFC PATCH 10/17] COLO ctl: introduce is_slave() and is_master() Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 14:55 ` Dr. David Alan Gilbert
2014-08-01 14:55 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-07-23 14:25 ` [RFC PATCH 11/17] COLO ctl: implement colo checkpoint protocol Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 15:03 ` Dr. David Alan Gilbert
2014-08-01 15:03 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-09-12 6:20 ` Hongyang Yang
2014-09-12 6:20 ` [Qemu-devel] " Hongyang Yang
2014-09-12 11:17 ` Dr. David Alan Gilbert
2014-09-12 11:17 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-09-12 11:40 ` Hongyang Yang
2014-09-12 11:40 ` [Qemu-devel] " Hongyang Yang
2014-09-12 11:57 ` Dr. David Alan Gilbert
2014-09-12 11:57 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-07-23 14:25 ` [RFC PATCH 12/17] COLO ctl: add a RunState RUN_STATE_COLO Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 15:48 ` Eric Blake
2014-07-23 15:48 ` Eric Blake
2014-07-23 14:25 ` [RFC PATCH 13/17] COLO ctl: implement colo save Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 15:07 ` Dr. David Alan Gilbert
2014-08-01 15:07 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-07-23 14:25 ` [RFC PATCH 14/17] COLO ctl: implement colo restore Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 14:25 ` [RFC PATCH 15/17] COLO save: reuse migration bitmap under colo checkpoint Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 15:09 ` Dr. David Alan Gilbert
2014-08-01 15:09 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-07-23 14:25 ` [RFC PATCH 16/17] COLO ram cache: implement colo ram cache on slaver Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-08-01 15:10 ` Dr. David Alan Gilbert
2014-08-01 15:10 ` [Qemu-devel] " Dr. David Alan Gilbert
2014-09-12 6:30 ` Hongyang Yang
2014-09-12 6:30 ` [Qemu-devel] " Hongyang Yang
2014-07-23 14:25 ` [RFC PATCH 17/17] HACK: trigger checkpoint every 500ms Yang Hongyang
2014-07-23 14:25 ` [Qemu-devel] " Yang Hongyang
2014-07-23 15:44 ` [Qemu-devel] [RFC PATCH 00/17] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service Eric Blake
2014-07-23 15:44 ` Eric Blake
2014-07-24 2:24 ` Hongyang Yang
2014-07-24 2:24 ` [Qemu-devel] " Hongyang Yang
2014-08-01 16:02 ` Dr. David Alan Gilbert [this message]
2014-08-01 16:02 ` Dr. David Alan Gilbert
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=20140801160242.GI2430@work-vm \
--to=dgilbert@redhat.com \
--cc=GuiJianfeng@cn.fujitsu.com \
--cc=eddie.dong@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mrhines@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.com \
--cc=yanghy@cn.fujitsu.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.