From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qemu 2.2.1
Date: Sat, 11 Apr 2015 17:00:44 +0200 [thread overview]
Message-ID: <5529371C.1000504@kamp.de> (raw)
In-Reply-To: <55291D68.8090506@kamp.de>
Am 11.04.2015 um 15:11 schrieb Peter Lieven:
> Am 09.04.2015 um 17:17 schrieb Paolo Bonzini:
>> On 09/04/2015 16:54, Peter Lieven wrote:
>>> #define BM_MIGRATION_COMPAT_STATUS_BITS \
>>> (IDE_RETRY_DMA | IDE_RETRY_PIO | \
>>> IDE_RETRY_READ | IDE_RETRY_FLUSH)
>>>
>>> Why is there no IDE_RETRY_WRITE ?
>> Because that's represented by none of read and flush being set. :)
>>
>>> Honestly, I have not yet understood that that
>>> BM_MIGRATION_COMPAT_STATUS_BITS is for.
>> It's just for migrations while the VM is stopped due to I/O errors
>> (rerror=stop/werror=stop).
> My migration problem seems to be a regression or incompatiblity in kvm-kmod. I started debugging
> with an old kvm module accidently. It seems to work with the old module shipped
> with the kernel (3.13) and fails with (3.19).
3.17 (kvm-kmod master) also seems to work. I had to move to 3.19 some time ago to
mititage another bug that triggered a new check in Qemu.
kvm-kmod next currently does not compile under my 3.13 host kernel. And according to
the buildbot output for kvm-kmod it seems to fail for almost all kernels <= 3.18.
I will keep my tests running with 3.17 kvm-kmod. Currently it has done nearly 1000 migrations
in a row without crashing.
Peter
next prev parent reply other threads:[~2015-04-11 15:00 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 ` [Qemu-devel] [Qemu-block] " John Snow
2015-04-06 19:02 ` 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 [this message]
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=5529371C.1000504@kamp.de \
--to=pl@kamp.de \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--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).