public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	jamie@audible.transient.net, kvm list <kvm@vger.kernel.org>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [bisected] KVM in 3.19-rc1 is completely broken
Date: Thu, 25 Dec 2014 16:57:53 +0800	[thread overview]
Message-ID: <549BD191.1010903@intel.com> (raw)
In-Reply-To: <549B6082.6030805@intel.com>



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 <tiejun.chen@intel.com>
>> wrote:
>>> On 2014/12/24 5:29, Andy Lutomirski wrote:
>>>>
>>>> On Tue, Dec 23, 2014 at 1:13 PM, Paolo Bonzini <pbonzini@redhat.com>
>>>> 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 <tiejun.chen@intel.com>
>>
>> I applied it by hand, and it survives extremely light testing.
>>
>> Tested-by: Andy Lutomirski <luto@amacapital.net>
>>
>
> 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

      reply	other threads:[~2014-12-25  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23  1:38 [bisected] KVM in 3.19-rc1 is completely broken Andy Lutomirski
2014-12-23  8:19 ` Chen, Tiejun
2014-12-23  8:30   ` Paolo Bonzini
2014-12-23  8:33   ` Andy Lutomirski
     [not found]     ` <CALCETrWJUUytHNjq_ft5Ajf6DZ47QoegohCLDj3p-g9FuTTWgA@mail.gmail.com>
2014-12-23 21:13       ` Paolo Bonzini
2014-12-23 21:29         ` Andy Lutomirski
2014-12-24  8:23           ` Chen, Tiejun
2014-12-24 17:11             ` Andy Lutomirski
2014-12-25  0:55               ` Chen, Tiejun
2014-12-25  8:57                 ` Chen, Tiejun [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=549BD191.1010903@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=imammedo@redhat.com \
    --cc=jamie@audible.transient.net \
    --cc=kvm@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox