On 02/24/2017 01:22 AM, Zhang Chen wrote: > We can call this qmp command to do checkpoint outside of qemu. > Xen colo will need this function. > > Signed-off-by: Zhang Chen <zhangchen.f...@cn.fujitsu.com> > Signed-off-by: Wen Congyang <wencongy...@gmail.com> > --- > migration/colo.c | 23 +++++++++++++++++++++++ > qapi-schema.json | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 72 insertions(+) >
> +++ b/qapi-schema.json
> @@ -5931,6 +5931,55 @@
> 'data': { 'enable': 'bool', 'primary': 'bool', '*failover' : 'bool' } }
>
> ##
> +# @ReplicationStatus:
> +#
> +# The result format for 'query-xen-replication-status'.
> +#
> +# @error: true to error, false to normal.
Maybe:
true if an error happened, false if replication is normal
Maintainer could touch that up during application, so it doesn't
necessarily require a v10.
> +##
> +# @query-xen-replication-status:
> +#
> +# Query replication status while the vm is running.
> +#
> +# Returns: A @ReplicationResult object showing the status.
> +#
> +# Example:
> +#
> +# -> { "execute": "query-xen-replication-status" }
> +# <- { "return": [ { "error": false },
> +# { "error": true } ] }
This example is bogus. The command does NOT return an array. It is
sufficient to use:
{ "return": { "error": false } }
but if you want, you could instead do:
{ "return": { "error": true, "desc": "..." } }
but if you do that, please be sure that desc matches an actual error
code that could occur, and not something made up.
If all you do is fix the example with the simpler "error":false (and
maybe the maintainer is okay doing that), then you can add:
Reviewed-by: Eric Blake <ebl...@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
