From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33474) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhYg3-0000kx-Vz for qemu-devel@nongnu.org; Mon, 13 Apr 2015 03:21:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YhYfz-0001Cn-Vg for qemu-devel@nongnu.org; Mon, 13 Apr 2015 03:21:03 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:35750 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhYfz-0001CG-La for qemu-devel@nongnu.org; Mon, 13 Apr 2015 03:20:59 -0400 Message-ID: <552B6E55.4050609@kamp.de> Date: Mon, 13 Apr 2015 09:20:53 +0200 From: Peter Lieven MIME-Version: 1.0 References: <5522D4BD.7080805@kamp.de> <5522D57B.3000203@redhat.com> <5522D85D.20907@kamp.de> <5522DA21.1010702@kamp.de> <20150407084303.GA2298@work-vm> <5523F38A.4090305@kamp.de> <20150407152957.GB2287@work-vm> <55242597.1000700@kamp.de> <20150407190112.GD2287@work-vm> <55267553.5000506@kamp.de> <20150409134339.GE2292@work-vm> <55269291.2000805@kamp.de> <55269823.5050904@redhat.com> <55291D68.8090506@kamp.de> <5529371C.1000504@kamp.de> In-Reply-To: <5529371C.1000504@kamp.de> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qemu 2.2.1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , "Dr. David Alan Gilbert" Cc: Marcelo Tosatti , John Snow , "qemu-devel@nongnu.org" , qemu-block@nongnu.org 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