From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Major KVM issues with kernel 4.5 on the host Date: Thu, 14 Apr 2016 19:30:43 +0200 Message-ID: <570FD3C3.2030709@redhat.com> References: <20160317165435.GB3022@torres.zugschlus.de> <20160317181128.GA30324@pd.tnic> <56EBD20A.1020608@redhat.com> <20160413183701.GC7600@torres.zugschlus.de> <570EADD2.8030300@redhat.com> <20160413222942.GD7600@torres.zugschlus.de> <570EEF6D.40307@redhat.com> <20160414164757.GA6484@torres.zugschlus.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Borislav Petkov , linux-kernel@vger.kernel.org, kvm ML To: Marc Haber Return-path: In-Reply-To: <20160414164757.GA6484@torres.zugschlus.de> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 14/04/2016 18:47, Marc Haber wrote: >> > Ok, then I guess bisection is needed. Please first try commit >> > 45bdbcfdf241. > I did git checkout 45bdbcfdf241 and built the resulting kernel > 4.4.0-rc5. This one has now been running for ten hours, which is > threefold the longest time that a faulty kernel has held before a VM > experienced corruption. So I guess, that one is fine. Interesting, this means it's not a KVM bug. You can ignore my patch from yesterday (though we'll get it in anyway). > Since 4.5.0-rc1 is bad, I guess I do: > > git checkout 45bdbcfdf241 > git bisect start > git bisect good > git bisect bad v4.5.0-rc1 This is correct but you also want to do git bisect good 4.4.0 git bisect good 4.4.0-rc5 so that bisection basically works through the commits in the merge window. Thanks, Paolo