Subject: Re: Major KVM issues with kernel 4.5 on the host
To: Marc Haber <mh+linux-kernel@zugschlus.de>
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>
Cc: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org,
        kvm ML <kvm@vger.kernel.org>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <570FD3C3.2030709@redhat.com>
Date: Thu, 14 Apr 2016 19:30:43 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <20160414164757.GA6484@torres.zugschlus.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 824
Lines: 30


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