From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:35454 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751007AbeBINGm (ORCPT
        <rfc822;stable@vger.kernel.org>); Fri, 9 Feb 2018 08:06:42 -0500
Date: Fri, 9 Feb 2018 14:06:40 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: stable@vger.kernel.org, nik@linuxbox.cz
Subject: Re: 4.14.x - KVM guests crashing
Message-ID: <20180209130640.GC6252@kroah.com>
References: <20180209095637.GA14309@pcnci.linuxbox.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180209095637.GA14309@pcnci.linuxbox.cz>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Fri, Feb 09, 2018 at 10:56:37AM +0100, Nikola Ciprich wrote:
> Hi,
> 
> not sure whether this is the best list to ask for that, but maybe
> somebody from -stable interested people has hit similar problem..
> 
> if it's not appropriate list to ask/report, please let me know
> 
> since we started rolling to 4.14.x kernels, we've experienced multiple
> KVM guest panics (with 4.14 on hosts)
> We've first hit it with 4.14.12, yesterday I had similar problem with 4.14.16. 

The KVM mailing list would probably be the best place
(kvm@vger.kernel.org), as we just backport existing upstream patches to
the stable kernels.

That being said, jumping from 4.4 to 4.14 is a very large leap (2 years
of development), it might be good if you can try something in the
middle?

Or, an earlier 4.14.y?  Try 4.14.3 or so and if that works, then it is
easier to use 'git bisect' to track down the offending patch.

thanks,

greg k-h