From: John Snow <jsnow@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-block@nongnu.org
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qemu 2.2.1
Date: Mon, 06 Apr 2015 14:50:35 -0400 [thread overview]
Message-ID: <5522D57B.3000203@redhat.com> (raw)
In-Reply-To: <5522D4BD.7080805@kamp.de>
On 04/06/2015 02:47 PM, Peter Lieven wrote:
> Hi all,
>
> is there a known issue in Qemu 2.2.1 where IDE stalls sometimes after a migration with Qemu 2.2.1?
> The migration succeeds, but it seems that the complete I/O is hanging. This happens only sometimes
> and only with extreme old Linux Guests (SLES 10 with Kernel 2.6.16) thus the IDE controller as
> storage controller for the system disk.
>
> Maybe this sounds familiar to someone.
>
> Thank you,
> Peter
>
It's news to me.
Is this a regression?
Any particular workload or reproducer?
--js
next prev parent reply other threads:[~2015-04-06 18:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 18:47 [Qemu-devel] Migration sometimes fails with IDE and Qemu 2.2.1 Peter Lieven
2015-04-06 18:50 ` John Snow [this message]
2015-04-06 19:02 ` [Qemu-devel] [Qemu-block] " Peter Lieven
2015-04-06 19:10 ` Peter Lieven
2015-04-07 8:43 ` Dr. David Alan Gilbert
2015-04-07 15:11 ` Peter Lieven
2015-04-07 15:14 ` Paolo Bonzini
2015-04-07 18:54 ` Peter Lieven
2015-04-07 15:29 ` Dr. David Alan Gilbert
2015-04-07 18:44 ` Peter Lieven
2015-04-07 18:56 ` John Snow
2015-04-07 19:02 ` Peter Lieven
2015-04-07 19:13 ` John Snow
2015-04-09 6:34 ` Peter Lieven
2015-04-09 12:46 ` Peter Lieven
2015-04-09 12:50 ` Paolo Bonzini
2015-04-07 19:01 ` Dr. David Alan Gilbert
2015-04-07 19:04 ` Peter Lieven
2015-04-09 12:49 ` Peter Lieven
2015-04-09 13:32 ` Peter Lieven
2015-04-09 13:43 ` Dr. David Alan Gilbert
2015-04-09 14:54 ` Peter Lieven
2015-04-09 15:17 ` Paolo Bonzini
2015-04-11 13:11 ` Peter Lieven
2015-04-11 15:00 ` Peter Lieven
2015-04-13 7:20 ` Peter Lieven
2015-04-07 20:05 ` Paolo Bonzini
2015-04-09 6:43 ` Peter Lieven
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=5522D57B.3000203@redhat.com \
--to=jsnow@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.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).