kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"KVM-ML (kvm@vger.kernel.org)" <kvm@vger.kernel.org>,
	Wanpeng Li <kernellwp@gmail.com>
Subject: Re: VMs freezing when host is running 4.14
Date: Wed, 22 Nov 2017 17:43:13 +0100	[thread overview]
Message-ID: <20171122164312.GA21279@flask> (raw)
In-Reply-To: <20171122155208.wdcmosxfpsjbwcrm@torres.zugschlus.de>

2017-11-22 16:52+0100, Marc Haber:
> On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > So all guest kernels are 4.14, or also other older kernel?
> 
> Guest kernels are also 4.14, but the issue disappears when the host is
> downgraded to an older kernel. I therefore reckoned that the guest
> kernel doesn't matter, but that was before I saw the trace in the log.

The two most suspicious patches since 4.13 (which I assume works) are

  664f8e26b00c ("KVM: X86: Fix loss of exception which has not yet been
  injected")

and

  9a6e7c39810e ("KVM: async_pf: Fix #DF due to inject "Page not Present"
  and "Page Ready" exceptions simultaneously")

please try reverting them to see if it helps,

thanks.

  reply	other threads:[~2017-11-22 16:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171121161821.b6k3hdl3wgia5f5q@torres.zugschlus.de>
     [not found] ` <20171122093945.5afa2di2g7qhf4eb@torres.zugschlus.de>
2017-11-22 15:04   ` VMs freezing when host is running 4.14 王金浦
2017-11-22 15:52     ` Marc Haber
2017-11-22 16:43       ` Radim Krčmář [this message]
2017-11-23 15:20         ` Marc Haber
2017-11-23 15:59           ` Radim Krčmář
2017-11-23 16:18             ` Liran Alon
2017-11-23 16:24               ` Radim Krčmář
2017-11-23 16:26                 ` Liran Alon
2017-11-24  8:08                   ` Marc Haber
2017-12-01 14:43     ` Marc Haber
2018-01-08  9:10       ` Marc Haber
2018-02-11 13:39         ` Marc Haber
2018-02-14  2:04           ` Josh Poimboeuf
2018-02-14  2:56             ` Haozhong Zhang
2018-02-14  3:17               ` Josh Poimboeuf
2018-02-14 10:23             ` Paolo Bonzini

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=20171122164312.GA21279@flask \
    --to=rkrcmar@redhat.com \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh+linux-kernel@zugschlus.de \
    /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;
as well as URLs for NNTP newsgroup(s).