From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Tiejun" Subject: Re: [bisected] KVM in 3.19-rc1 is completely broken Date: Thu, 25 Dec 2014 16:57:53 +0800 Message-ID: <549BD191.1010903@intel.com> References: <54992591.5070206@intel.com> <1967770651.2358249.1419369239480.JavaMail.zimbra@redhat.com> <549A781A.6010505@intel.com> <549B6082.6030805@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini , jamie@audible.transient.net, kvm list , Igor Mammedov To: Andy Lutomirski Return-path: Received: from mga03.intel.com ([134.134.136.65]:19370 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751904AbaLYI54 (ORCPT ); Thu, 25 Dec 2014 03:57:56 -0500 In-Reply-To: <549B6082.6030805@intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2014/12/25 8:55, Chen, Tiejun wrote: > > > On 2014/12/25 1:11, Andy Lutomirski wrote: >> On Wed, Dec 24, 2014 at 12:23 AM, Chen, Tiejun >> wrote: >>> On 2014/12/24 5:29, Andy Lutomirski wrote: >>>> >>>> On Tue, Dec 23, 2014 at 1:13 PM, Paolo Bonzini >>>> wrote: >>>>> >>>>> >>>>>> I can reproduce it using the same steps on a Sandy Bridge laptop, >>>>>> with >>>>>> whatever QEMU is packaged in Fedora 21. I attached the config. >>>>>> >>>>>> I also submitted a virtme update for Fedora Rawhide and 21 (20 is >>>>>> still building) in case it helps. The build is here: >>>>>> >>>>>> http://koji.fedoraproject.org/koji/buildinfo?buildID=600732 >>>>> >>>>> >>>>> The other reporter bisected it to >>>>> 0e60b0799fedc495a5c57dbd669de3c10d72edd2. Can you try its parent? >>>> >>>> >>>> That's what I bisected it to. The parent works. >>>> >>>>> >>>>> Also, does it break with 3.18 host and 3.19-rc1 guest, or with >>>>> 3.19-rc1 host and 3.18 guest? (Sorry I should do this myself >>>>> but I'm a bit swamped due to vacation until Jan 6th). >>>>> >>>> >>>> The breakage is with 3.17.7-something L0 and the same test kernel as >>>> L1 and L2. I think it breaks the same way with 3.19-rc1 as host and >>>> guest without any nesting, but that's awkward to test right now. >>>> >>> >>> >>> Andy, >>> >>> Could you try this? >>> >>> Signed-off-by: Tiejun Chen >> >> I applied it by hand, and it survives extremely light testing. >> >> Tested-by: Andy Lutomirski >> > > Looks good so thanks for your validation. > I refine that I posted that fix in another thread since looks that will broken !next case. And I myself already run those test instructions you showed previously, now looks good. Tiejun