qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qem


From: Peter Lieven
Subject: Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qemu 2.2.1
Date: Mon, 13 Apr 2015 09:20:53 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

Am 11.04.2015 um 17:00 schrieb Peter Lieven:
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 meanwhile managed to compile the kvm-kmod next. The bug is still in there.

I will now try kvm-kmod master with

KVM: x86: update masterclock values on TSC writes

on top.

Help appreciated.

Thanks,
Peter




reply via email to

[Prev in Thread] Current Thread [Next in Thread]