qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: lizhijian@cn.fujitsu.com, quintela@redhat.com,
	yunhong.jiang@intel.com, eddie.dong@intel.com,
	peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
	arei.gonglei@huawei.com, amit.shah@redhat.com,
	Yang Hongyang <yanghy@cn.fujitsu.com>,
	laijs@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH COLO-Frame v6 03/31] COLO: migrate colo related info to slave
Date: Mon, 6 Jul 2015 15:26:13 +0800	[thread overview]
Message-ID: <559A2D95.1060105@huawei.com> (raw)
In-Reply-To: <20150703180337.GI2142@work-vm>

On 2015/7/4 2:03, Dr. David Alan Gilbert wrote:
> * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
>> We can know if VM in destination should go into COLO mode by refer to
>> the info that has been migrated from PVM.
>>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
>> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
>> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>> ---
>>   include/migration/migration-colo.h |  2 ++
>>   migration/Makefile.objs            |  1 +
>>   migration/colo-comm.c              | 47 ++++++++++++++++++++++++++++++++++++++
>>   trace-events                       |  3 +++
>>   vl.c                               |  5 +++-
>>   5 files changed, 57 insertions(+), 1 deletion(-)
>>   create mode 100644 migration/colo-comm.c
>>
>> diff --git a/include/migration/migration-colo.h b/include/migration/migration-colo.h
>> index c6d0c51..e20a0c1 100644
>> --- a/include/migration/migration-colo.h
>> +++ b/include/migration/migration-colo.h
>> @@ -14,7 +14,9 @@
>>   #define QEMU_MIGRATION_COLO_H
>>
>>   #include "qemu-common.h"
>> +#include "migration/migration.h"
>>
>>   bool colo_supported(void);
>> +void colo_info_mig_init(void);
>>
>>   #endif
>> diff --git a/migration/Makefile.objs b/migration/Makefile.objs
>> index 5a25d39..cb7bd30 100644
>> --- a/migration/Makefile.objs
>> +++ b/migration/Makefile.objs
>> @@ -1,5 +1,6 @@
>>   common-obj-y += migration.o tcp.o
>>   common-obj-$(CONFIG_COLO) += colo.o
>> +common-obj-y += colo-comm.o
>>   common-obj-y += vmstate.o
>>   common-obj-y += qemu-file.o qemu-file-buf.o qemu-file-unix.o qemu-file-stdio.o
>>   common-obj-y += xbzrle.o
>> diff --git a/migration/colo-comm.c b/migration/colo-comm.c
>> new file mode 100644
>> index 0000000..0b76eb4
>> --- /dev/null
>> +++ b/migration/colo-comm.c
>> @@ -0,0 +1,47 @@
>> +/*
>> + * COarse-grain LOck-stepping Virtual Machines for Non-stop Service (COLO)
>> + * (a.k.a. Fault Tolerance or Continuous Replication)
>> + *
>> + * Copyright (c) 2015 HUAWEI TECHNOLOGIES CO., LTD.
>> + * Copyright (c) 2015 FUJITSU LIMITED
>> + * Copyright (c) 2015 Intel Corporation
>> + *
>> + * This work is licensed under the terms of the GNU GPL, version 2 or
>> + * later. See the COPYING file in the top-level directory.
>> + *
>> + */
>> +
>> +#include <migration/migration-colo.h>
>> +#include "trace.h"
>> +
>> +static bool colo_requested;
>> +
>> +/* save */
>> +static void colo_info_save(QEMUFile *f, void *opaque)
>> +{
>> +    qemu_put_byte(f, migrate_enable_colo());
>> +}
>> +
>> +/* restore */
>> +static int colo_info_load(QEMUFile *f, void *opaque, int version_id)
>> +{
>> +    int value = qemu_get_byte(f);
>> +
>> +    if (value && !colo_requested) {
>> +        trace_colo_info_load("COLO request!");
>> +    }
>> +    colo_requested = value;
>> +
>> +    return 0;
>> +}
>> +
>> +static SaveVMHandlers savevm_colo_info_handlers = {
>> +    .save_state = colo_info_save,
>> +    .load_state = colo_info_load,
>> +};
>> +
>> +void colo_info_mig_init(void)
>> +{
>> +    register_savevm_live(NULL, "colo", -1, 1,
>> +                         &savevm_colo_info_handlers, NULL);
>> +}
>> diff --git a/trace-events b/trace-events
>> index 52b7efa..3f63019 100644
>> --- a/trace-events
>> +++ b/trace-events
>> @@ -1466,6 +1466,9 @@ rdma_start_incoming_migration_after_rdma_listen(void) ""
>>   rdma_start_outgoing_migration_after_rdma_connect(void) ""
>>   rdma_start_outgoing_migration_after_rdma_source_init(void) ""
>>
>> +# migration/colo-comm.c
>> +colo_info_load(const char *msg) "%s"
>> +
>>   # kvm-all.c
>>   kvm_ioctl(int type, void *arg) "type 0x%x, arg %p"
>>   kvm_vm_ioctl(int type, void *arg) "type 0x%x, arg %p"
>> diff --git a/vl.c b/vl.c
>> index 2201e27..988567a 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -90,6 +90,7 @@ int main(int argc, char **argv)
>>   #include "sysemu/dma.h"
>>   #include "audio/audio.h"
>>   #include "migration/migration.h"
>> +#include "migration/migration-colo.h"
>>   #include "sysemu/kvm.h"
>>   #include "qapi/qmp/qjson.h"
>>   #include "qemu/option.h"
>> @@ -4261,7 +4262,9 @@ int main(int argc, char **argv, char **envp)
>>
>>       blk_mig_init();
>>       ram_mig_init();
>> -
>> +#ifdef CONFIG_COLO
>> +    colo_info_mig_init();
>> +#endif
>
> Does't this still break migration compatibility?  I wouldn't

Yes, it will break migration if the QEMU in destination and source not enable/disable (configure) this
feature together, also not compatible with old version on migration.

> want to have to have two QEMU builds on a system, one built with COLO
> and one built without COLO.   You need to arrange for the
> section to only be sent if COLO is enabled (i.e. migrate_set_capability colo on).
> One way to do that would be to use the new QEMU optional sections
> that Juan added recently.
>

Hmm, his method can address the above problems, (though, we will still fail when we configure
with --enable-colo in source side and --disable-colo in destination, but that is what
we want, we should not go into colo mode if secondary host is not enable this feature).
I will look into his patch, and fix that in next version, thanks,

zhanghailiang

> Dave
>
>>       /* If the currently selected machine wishes to override the units-per-bus
>>        * property of its default HBA interface type, do so now. */
>>       if (machine_class->units_per_default_bus) {
>> --
>> 1.7.12.4
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> .
>

  reply	other threads:[~2015-07-06  7:26 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18  8:58 [Qemu-devel] [PATCH COLO-Frame v6 00/31] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 01/31] configure: Add parameter for configure to enable/disable COLO support zhanghailiang
2015-07-03 17:51   ` Dr. David Alan Gilbert
2015-07-06  5:27     ` zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 02/31] migration: Introduce capability 'colo' to migration zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 03/31] COLO: migrate colo related info to slave zhanghailiang
2015-07-03 18:03   ` Dr. David Alan Gilbert
2015-07-06  7:26     ` zhanghailiang [this message]
2015-07-06  8:29       ` Dr. David Alan Gilbert
2015-07-06  8:54         ` zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 04/31] migration: Integrate COLO checkpoint process into migration zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 05/31] migration: Integrate COLO checkpoint process into loadvm zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 06/31] COLO: Implement colo checkpoint protocol zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 07/31] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 08/31] QEMUSizedBuffer: Introduce two help functions for qsb zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 09/31] COLO: Save VM state to slave when do checkpoint zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 10/31] COLO RAM: Load PVM's dirty page into SVM's RAM cache temporarily zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 11/31] COLO VMstate: Load VM state into qsb before restore it zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 12/31] arch_init: Start to trace dirty pages of SVM zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 13/31] COLO RAM: Flush cached RAM into SVM's memory zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 14/31] COLO failover: Introduce a new command to trigger a failover zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 15/31] COLO failover: Implement COLO primary/secondary vm failover work zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 16/31] qmp event: Add event notification for COLO error zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 17/31] COLO failover: Don't do failover during loading VM's state zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 18/31] COLO: Add new command parameter 'colo_nicname' 'colo_script' for net zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 19/31] COLO NIC: Init/remove colo nic devices when add/cleanup tap devices zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 20/31] tap: Make launch_script() public zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 21/31] COLO NIC: Implement colo nic device interface configure() zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 22/31] COLO NIC : Implement colo nic init/destroy function zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 23/31] COLO NIC: Some init work related with proxy module zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 24/31] COLO: Handle nfnetlink message from " zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 25/31] COLO: Do checkpoint according to the result of packets comparation zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 26/31] COLO: Improve checkpoint efficiency by do additional periodic checkpoint zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 27/31] COLO: Add colo-set-checkpoint-period command zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 28/31] COLO NIC: Implement NIC checkpoint and failover zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 29/31] COLO: Disable qdev hotplug when VM is in COLO mode zhanghailiang
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 30/31] COLO: Implement shutdown checkpoint zhanghailiang
2015-06-18 14:55   ` Paolo Bonzini
2015-06-18  8:58 ` [Qemu-devel] [PATCH COLO-Frame v6 31/31] COLO: Add block replication into colo process zhanghailiang
2015-06-30 16:38 ` [Qemu-devel] [PATCH COLO-Frame v6 00/31] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service Dr. David Alan Gilbert
2015-07-01  6:36   ` zhanghailiang

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=559A2D95.1060105@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=amit.shah@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yanghy@cn.fujitsu.com \
    --cc=yunhong.jiang@intel.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 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).