From: Charles Duffy <Charles_Duffy@messageone.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Live migration broken when under heavy IO
Date: Tue, 16 Jun 2009 13:19:05 -0500 [thread overview]
Message-ID: <h18nmd$lvb$1@ger.gmane.org> (raw)
In-Reply-To: <4A36B025.2080602@us.ibm.com>
I'm not sure if this is related, but to comment --
I'm seeing what appears to be occasional dropped I/O on non-live
migration -- that is to say, stop, migrate-to-disk, shuffle files
around, migrate-from-disk, cont. I have not yet been able to reproduce
this with cache=off.
As I understand it, the bulk of discussion in this thread is about I/O
submitted by the guest after the migration starts; as I'm stopping the
guest CPU _before_ initiating migration, there would appear to be
outstanding issues not limited to this scenario.
[qemu-kvm-0.10.5, IDE, qcow2]
prev parent reply other threads:[~2009-06-16 18:19 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
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 [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='h18nmd$lvb$1@ger.gmane.org' \
--to=charles_duffy@messageone.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).