xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Cc: Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"eddie . dong" <eddie.dong@intel.com>,
	Yang Hongyang <imhy.yang@gmail.com>,
	Xen devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 2/3] Add Xen colo support for qemu-upstream colo codes
Date: Thu, 1 Dec 2016 13:20:18 +0000	[thread overview]
Message-ID: <20161201132018.GB394@citrix.com> (raw)
In-Reply-To: <1480499272-11893-3-git-send-email-zhangchen.fnst@cn.fujitsu.com>

On Wed, Nov 30, 2016 at 05:47:51PM +0800, Zhang Chen wrote:
> Because of qemu codes update, we update Xen colo block codes
> 
> Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>

COLO being an experimental feature means that you can change it at will,
so for both patches:

Acked-by: Wei Liu <wei.liu2@citrix.com>

But, this sort of patch does make me wonder how QEMU handles backward
compatibility for command line options...

> ---
>  tools/libxl/libxl_colo_qdisk.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/libxl/libxl_colo_qdisk.c b/tools/libxl/libxl_colo_qdisk.c
> index d271d1f..300bff2 100644
> --- a/tools/libxl/libxl_colo_qdisk.c
> +++ b/tools/libxl/libxl_colo_qdisk.c
> @@ -169,9 +169,9 @@ static void colo_qdisk_save_preresume(libxl__egc *egc,
>      /* qmp command doesn't support the driver "nbd" */
>      node = GCSPRINTF("colo_node%d",
>                       libxl__device_disk_dev_number(disk->vdev, NULL, NULL));
> -    cmd = GCSPRINTF("drive_add buddy driver=replication,mode=primary,"
> +    cmd = GCSPRINTF("drive_add -n buddy driver=replication,mode=primary,"
>                      "file.driver=nbd,file.host=%s,file.port=%d,"
> -                    "file.export=%s,node-name=%s,if=none",
> +                    "file.export=%s,node-name=%s",
>                      host, port, export_name, node);
>      ret = libxl__qmp_hmp(gc, domid, cmd, NULL);
>      if (ret)
> -- 
> 2.7.4
> 
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-12-01 13:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30  9:47 [PATCH 0/3] Support the latest version of qemu COLO Zhang Chen
2016-11-30  9:47 ` [PATCH 1/3] Don't create default ioreq server Zhang Chen
2016-11-30 12:25   ` Andrew Cooper
2016-12-07  2:46     ` Wen Congyang
2016-12-01 13:19   ` Wei Liu
2016-12-09  6:38     ` Zhang Chen
2016-12-09 16:13       ` Konrad Rzeszutek Wilk
2016-12-09 16:43         ` Paul Durrant
2016-12-09 17:21           ` Konrad Rzeszutek Wilk
2016-12-09 17:37             ` Paul Durrant
2016-12-12 18:03           ` Ian Jackson
2016-12-12 18:08             ` Paul Durrant
2016-11-30  9:47 ` [PATCH 2/3] Add Xen colo support for qemu-upstream colo codes Zhang Chen
2016-12-01 13:20   ` Wei Liu [this message]
2016-12-12 10:37     ` Wei Liu
2016-12-13  1:46       ` Zhang Chen
2016-11-30  9:47 ` [PATCH 3/3] Add COLO replication top-id support 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=20161201132018.GB394@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=imhy.yang@gmail.com \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xiecl.fnst@cn.fujitsu.com \
    --cc=zhangchen.fnst@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 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).