From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [CFR 4/10] qmp: migrate_set_downtime command
Date: Thu, 17 Jun 2010 20:59:23 +0100 [thread overview]
Message-ID: <AANLkTilD3Jn1ulEfwUXADI1jEPbR2kJTdIQKvV7_tMLS@mail.gmail.com> (raw)
In-Reply-To: <1276703160-7894-5-git-send-email-stefanha@linux.vnet.ibm.com>
On Wed, Jun 16, 2010 at 4:45 PM, Stefan Hajnoczi
<stefanha@linux.vnet.ibm.com> wrote:
> migrate_set_downtime
> --------------------
>
> Set maximum tolerated downtime (in seconds) for migrations.
>
> Arguments:
>
> - "value": maximum downtime (json-number)
>
> Example:
>
> -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
> <- { "return": {} }
What are the semantics of this value? I imagine it has to do with the rate of
transferring dirty pages and deciding when to suspend the machine to perform
the final steps of migration.
Is there a need to query this value, too? The ability to set the value is
probably enough, I can't think of a situation where you need to query it rather
than just setting a new value.
Can this value be changed once migration is in progress?
Stefan
next prev parent reply other threads:[~2010-06-17 19:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:45 [Qemu-devel] [CFR 0/10] QMP specification review (Part 2) Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 1/10] qmp: getfd command Stefan Hajnoczi
2010-06-16 18:47 ` [Qemu-devel] " Anthony Liguori
2010-06-17 19:49 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 2/10] qmp: memsave command Stefan Hajnoczi
2010-06-16 18:49 ` [Qemu-devel] " Anthony Liguori
2010-06-17 19:57 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 3/10] qmp: migrate_cancel command Stefan Hajnoczi
2010-06-16 18:49 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:45 ` [Qemu-devel] [CFR 4/10] qmp: migrate_set_downtime command Stefan Hajnoczi
2010-06-16 18:50 ` [Qemu-devel] " Anthony Liguori
2010-06-17 19:59 ` Stefan Hajnoczi [this message]
2010-06-16 15:45 ` [Qemu-devel] [CFR 5/10] qmp: migrate_set_speed command Stefan Hajnoczi
2010-06-16 18:51 ` [Qemu-devel] " Anthony Liguori
2010-06-17 20:00 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 6/10] qmp: migrate command Stefan Hajnoczi
2010-06-16 18:52 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:45 ` [Qemu-devel] [CFR 7/10] qmp: netdev_add command Stefan Hajnoczi
2010-06-16 18:53 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:45 ` [Qemu-devel] [CFR 8/10] qmp: netdev_del command Stefan Hajnoczi
2010-06-16 18:53 ` [Qemu-devel] " Anthony Liguori
2010-06-17 20:01 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 9/10] qmp: pmemsave command Stefan Hajnoczi
2010-06-16 18:53 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:46 ` [Qemu-devel] [CFR 10/10] qmp: query_balloon command Stefan Hajnoczi
2010-06-16 18:54 ` [Qemu-devel] " Anthony Liguori
2010-06-17 20:03 ` Stefan Hajnoczi
2010-06-16 18:12 ` [Qemu-devel] [CFR 0/10] QMP specification review (Part 2) Blue Swirl
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=AANLkTilD3Jn1ulEfwUXADI1jEPbR2kJTdIQKvV7_tMLS@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).