From: Jiri Denemark <jdenemar@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kwolf@redhat.com, Jes.Sorensen@redhat.com, dlaor@redhat.com,
qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [patch 6/7] QEMU live block copy (update)
Date: Tue, 7 Jun 2011 12:15:55 +0200 [thread overview]
Message-ID: <20110607101555.GO514380@orkuz.home> (raw)
In-Reply-To: <20110606170344.GA30636@amt.cnet>
On Mon, Jun 06, 2011 at 14:03:44 -0300, Marcelo Tosatti wrote:
...
> SQMP
> +query-block-copy
> +-------------
> +
> +Live block copy status.
> +
> +Each block copy instance information is stored in a json-object and the returned
> +value is a json-array of all instances.
> +
> +Each json-object contains the following:
> +
> +- "device": device name (json-string)
> +- "status": block copy status (json-string)
> + - Possible values: "active", "failed", "mirrored", "completed", meaning:
> + - failed: block copy failed.
> + - active: block copy active, copying to destination image.
> + - mirrored: block copy active, finished copying to destination
> + image, writes are mirrored.
> + - completed: block copy completed.
> +
> +- "info": A json-object with the statistics information, if status is "active":
> + - "percentage": percentage completed (json-int)
> +
> +Example:
> +
> +Block copy for "ide1-hd0" active and block copy for "ide1-hd1" failed:
> +
> +-> { "execute": "query-block-copy" }
> +<- {
> + "return":[
> + {"device":"ide1-hd0",
> + "status":"active",
> + "info":{
> + "percentage":23,
> + }
> + },
What about using the same form of progress reporting as used by query-migrate?
That is, instead of
"info":{
"percentage":23
}
the following would be reported:
"disk":{
"transferred":123,
"remaining":123,
"total":246
}
One can trivially compute percentage from that but it's impossible to get this
kind of data when only percentage is reported. And total can even change in
time if needed (just like it changes during migration).
> + {"device":"ide1-hd1",
> + "status":"failed"
> + }
Is there any way we can get the exact error which made it fail, such as EPERM
or ENOSPC?
> + ]
> + }
> +
> +EQMP
Jirka
next prev parent reply other threads:[~2011-06-07 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 16:55 [Qemu-devel] [patch 0/7] live block copy (v4) Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 1/7] add migration_active function Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 2/7] Add blkmirror block driver Marcelo Tosatti
2011-06-06 21:52 ` malc
2011-06-07 10:25 ` Stefan Hajnoczi
2011-06-06 16:55 ` [Qemu-devel] [patch 3/7] Add error messages for live block copy Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 4/7] Add blkdebug points " Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 5/7] Add vmstop code " Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 6/7] QEMU " Marcelo Tosatti
2011-06-06 17:03 ` [Qemu-devel] [patch 6/7] QEMU live block copy (update) Marcelo Tosatti
2011-06-07 10:15 ` Jiri Denemark [this message]
2011-06-15 15:49 ` Marcelo Tosatti
2011-06-15 15:51 ` Marcelo Tosatti
2011-06-07 12:15 ` [Qemu-devel] [patch 6/7] QEMU live block copy Stefan Hajnoczi
2011-06-08 15:10 ` Jagane Sundar
2011-06-08 16:18 ` Stefan Hajnoczi
2011-06-09 15:42 ` Jagane Sundar
2011-06-15 16:59 ` Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 7/7] do not allow migration if block copy in progress Marcelo Tosatti
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=20110607101555.GO514380@orkuz.home \
--to=jdenemar@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=kwolf@redhat.com \
--cc=mtosatti@redhat.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).