From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: Live migration broken when under heavy IO
Date: Tue, 16 Jun 2009 12:13:50 +0300 [thread overview]
Message-ID: <4A37624E.4040503@redhat.com> (raw)
In-Reply-To: <4A37618E.6040606@redhat.com>
On 06/16/2009 12:10 PM, Avi Kivity wrote:
>> Does anyone have a clever idea how to fix this without just waiting
>> for all IO requests to complete?
>
> What's wrong with waiting for requests to complete? It should take a
> few tens of milliseconds.
>
> We could start throttling requests late in the live stage, but I don't
> really see the point.
Well, we can introduce a new live stage, where we migrate RAM and
complete block requests, but the vm is otherwise stopped. This allows
the flush to overlap with sending memory dirtied by the flush, reducing
some downtime. Since block requests can dirty large amounts of memory,
this may be significant.
We can even keep the vcpu alive, only blocking new block requests, but
that may cause dirty RAM divergence.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-16 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 20:33 [Qemu-devel] Live migration broken when under heavy IO Anthony Liguori
2009-06-15 20:48 ` Glauber Costa
2009-06-16 9:10 ` [Qemu-devel] " Avi Kivity
2009-06-16 9:13 ` Avi Kivity [this message]
2009-06-16 12:50 ` Anthony Liguori
2009-06-16 12:54 ` Avi Kivity
2009-06-16 12:57 ` Anthony Liguori
2009-06-16 13:12 ` Avi Kivity
2009-06-16 18:19 ` Charles Duffy
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=4A37624E.4040503@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--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).