From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Lieven Subject: Re: Help debugging a regression in KVM Module Date: Fri, 14 Aug 2015 21:36:51 +0200 Message-ID: <55CE4353.6050808@kamp.de> References: <55CDCCE6.90102@kamp.de> <1104465571.12477184.1439557273772.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx01.kamp.de ([82.141.2.16]:53624 "EHLO mx01.kamp.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750703AbbHNTgz (ORCPT ); Fri, 14 Aug 2015 15:36:55 -0400 In-Reply-To: <1104465571.12477184.1439557273772.JavaMail.zimbra@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Am 14.08.2015 um 15:01 schrieb Paolo Bonzini: > > ----- Original Message ----- >> From: "Peter Lieven" >> To: qemu-devel@nongnu.org, kvm@vger.kernel.org >> Cc: "Paolo Bonzini" >> Sent: Friday, August 14, 2015 1:11:34 PM >> Subject: Help debugging a regression in KVM Module >> >> Hi, >> >> some time a go I stumbled across a regression in the KVM Module that has been >> introduced somewhere >> between 3.17 and 3.19. >> >> I have a rather old openSUSE guest with an XFS filesystem which realiably >> crashes after some live migrations. >> I originally believed that the issue might be related to my setup with a 3.12 >> host kernel and kvm-kmod 3.19, >> but I now found that it is also still present with a 3.19 host kernel with >> included 3.19 kvm module. >> >> My idea was to continue testing on a 3.12 host kernel and then bisect all >> commits to the kvm related parts. >> >> Now my question is how to best bisect only kvm related changes (those that go >> into kvm-kmod)? > I haven't forgotten this. Sorry. :( > > Unfortunately I'll be away for three weeks, but I'll make it a priority > when I'm back. Its not time critical, but I think its worth investigating as it might affect other systems as well - and maybe XFS is only very sensitive. I suppose you are going on vacation. Enjoy! Peter From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQKmn-0001Xf-2K for qemu-devel@nongnu.org; Fri, 14 Aug 2015 15:37:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZQKmf-0002d7-MP for qemu-devel@nongnu.org; Fri, 14 Aug 2015 15:37:04 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:41313 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQKmf-0002bz-Bl for qemu-devel@nongnu.org; Fri, 14 Aug 2015 15:36:57 -0400 Message-ID: <55CE4353.6050808@kamp.de> Date: Fri, 14 Aug 2015 21:36:51 +0200 From: Peter Lieven MIME-Version: 1.0 References: <55CDCCE6.90102@kamp.de> <1104465571.12477184.1439557273772.JavaMail.zimbra@redhat.com> In-Reply-To: <1104465571.12477184.1439557273772.JavaMail.zimbra@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Help debugging a regression in KVM Module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org Am 14.08.2015 um 15:01 schrieb Paolo Bonzini: > > ----- Original Message ----- >> From: "Peter Lieven" >> To: qemu-devel@nongnu.org, kvm@vger.kernel.org >> Cc: "Paolo Bonzini" >> Sent: Friday, August 14, 2015 1:11:34 PM >> Subject: Help debugging a regression in KVM Module >> >> Hi, >> >> some time a go I stumbled across a regression in the KVM Module that has been >> introduced somewhere >> between 3.17 and 3.19. >> >> I have a rather old openSUSE guest with an XFS filesystem which realiably >> crashes after some live migrations. >> I originally believed that the issue might be related to my setup with a 3.12 >> host kernel and kvm-kmod 3.19, >> but I now found that it is also still present with a 3.19 host kernel with >> included 3.19 kvm module. >> >> My idea was to continue testing on a 3.12 host kernel and then bisect all >> commits to the kvm related parts. >> >> Now my question is how to best bisect only kvm related changes (those that go >> into kvm-kmod)? > I haven't forgotten this. Sorry. :( > > Unfortunately I'll be away for three weeks, but I'll make it a priority > when I'm back. Its not time critical, but I think its worth investigating as it might affect other systems as well - and maybe XFS is only very sensitive. I suppose you are going on vacation. Enjoy! Peter