From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
cui@nutanix.com, Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
felipe@nutanix.com
Subject: Re: [Qemu-devel] Live migration without bdrv_drain_all()
Date: Wed, 12 Oct 2016 15:09:56 +0200 [thread overview]
Message-ID: <20161012130956.GA15590@stefanha-x1.localdomain> (raw)
In-Reply-To: <20160927094848.GA20968@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Tue, Sep 27, 2016 at 10:48:48AM +0100, Daniel P. Berrange wrote:
> On Mon, Aug 29, 2016 at 11:06:48AM -0400, Stefan Hajnoczi wrote:
> > At KVM Forum an interesting idea was proposed to avoid
> > bdrv_drain_all() during live migration. Mike Cui and Felipe Franciosi
> > mentioned running at queue depth 1. It needs more thought to make it
> > workable but I want to capture it here for discussion and to archive
> > it.
> >
> > bdrv_drain_all() is synchronous and can cause VM downtime if I/O
> > requests hang. We should find a better way of quiescing I/O that is
> > not synchronous. Up until now I thought we should simply add a
> > timeout to bdrv_drain_all() so it can at least fail (and live
> > migration would fail) if I/O is stuck instead of hanging the VM. But
> > the following approach is also interesting...
>
> How would you decide what an acceptable timeout is for the drain
> operation ?
Same as most timeouts: an arbitrary number :(.
> At what point does a stuck drain op cause the VM
> to stall ?
The drain call has acquired the QEMU global mutex. Any vmexit that
requires taking the QEMU global mutex will hang that thread (i.e. vcpu
thread).
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-10-12 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 15:06 [Qemu-devel] Live migration without bdrv_drain_all() Stefan Hajnoczi
2016-08-29 18:56 ` Felipe Franciosi
2016-09-27 9:27 ` Stefan Hajnoczi
2016-09-27 9:51 ` Daniel P. Berrange
2016-09-27 9:54 ` Dr. David Alan Gilbert
2016-09-28 9:03 ` Juan Quintela
2016-09-28 10:00 ` Felipe Franciosi
2016-09-28 10:23 ` Daniel P. Berrange
2016-09-27 9:48 ` Daniel P. Berrange
2016-10-12 13:09 ` Stefan Hajnoczi [this message]
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=20161012130956.GA15590@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=cui@nutanix.com \
--cc=felipe@nutanix.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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).