From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40852) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQCtm-0007qU-Nr for qemu-devel@nongnu.org; Fri, 14 Aug 2015 07:11:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZQCth-00079Z-LK for qemu-devel@nongnu.org; Fri, 14 Aug 2015 07:11:46 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:48087 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQCth-00078l-8H for qemu-devel@nongnu.org; Fri, 14 Aug 2015 07:11:41 -0400 Message-ID: <55CDCCE6.90102@kamp.de> Date: Fri, 14 Aug 2015 13:11:34 +0200 From: Peter Lieven MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Help debugging a regression in KVM Module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" Cc: Paolo Bonzini 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)? Thanks, Peter