Paolo, On Thu, 25 Jul 2019 at 19:17, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > On 25/07/19 13:34, Greg Kroah-Hartman wrote: > > Any chance you can run 'git bisect' to find the offending patch? Or > > just try reverting a few, you can ignore the ppc ones, so that only > > leaves you 7 different commits. > > > > Does this same test pass in 5.3-rc1? Yes. same test pass on 5.3-rc1 kvm unit test always fetching master branch and at tip runs the latest test code on all branches mainline 5.3-rc1 and stable-rc-5.2 branch > > Anders, are you running the same kvm-unit-tests commit that passed for > 5.2.2? My suspicion is that your previous test didn't have this commit No. I see two extra test code commits for 5.2.3 Re-tested 5.2.2 with tip of kvm unit tests sources and vmx test FAILED [1]. Greg, This investigation confirms it is a new test code failure on stable-rc 5.2.3 > since the symptoms match and the corresponding fix was made in 5.3. Thanks for your findings. > Paolo - Naresh [1] https://lkft.validation.linaro.org/scheduler/job/837811
