From: Paolo Bonzini <pbonzini@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Virtio 9p live migration patches
Date: Thu, 04 Apr 2013 15:42:06 +0200 [thread overview]
Message-ID: <515D832E.6040603@redhat.com> (raw)
In-Reply-To: <20130404123738.GD4250@irqsave.net>
Il 04/04/2013 14:37, Benoît Canet ha scritto:
> We also need to ensure new 9p request are blocked.
Migration runs with the VM paused. It would be simplest to flush all
the requests before migrating, that's what the block layer does. (The
migration of requests we have in virtio-blk, scsi-disk etc. is only for
rerror/werror=stop; it is not invoked in the common case).
Paolo
next prev parent reply other threads:[~2013-04-04 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 15:33 [Qemu-devel] Virtio 9p live migration patches Benoît Canet
2013-04-02 18:30 ` Aneesh Kumar K.V
2013-04-02 19:33 ` Benoît Canet
2013-04-03 6:33 ` Aneesh Kumar K.V
2013-04-04 12:37 ` Benoît Canet
2013-04-04 13:42 ` Paolo Bonzini [this message]
2013-04-04 14:08 ` Benoît Canet
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=515D832E.6040603@redhat.com \
--to=pbonzini@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benoit.canet@irqsave.net \
--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).