----- Original Message ----- > From: "Peter Lieven" <pl@xxxxxxx> > To: qemu-devel@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx > Cc: "Paolo Bonzini" <pbonzini@xxxxxxxxxx> > 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. Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
