All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Fri, 9 Feb 2018 14:06:40 +0100	[thread overview]
Message-ID: <20180209130640.GC6252@kroah.com> (raw)
In-Reply-To: <20180209095637.GA14309@pcnci.linuxbox.cz>

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

  reply	other threads:[~2018-02-09 13:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  9:56 4.14.x - KVM guests crashing Nikola Ciprich
2018-02-09 13:06 ` Greg KH [this message]
2018-02-09 13:10   ` Nikola Ciprich
2018-02-10 21:52   ` Christoph Biedl
2018-02-11  7:25     ` Nikola Ciprich
2018-02-13 15:43       ` Greg KH
2018-02-13 15:59         ` Nikola Ciprich
2018-02-15  7:53           ` Greg KH
2018-02-14 22:29       ` Christoph Biedl

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=20180209130640.GC6252@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=nik@linuxbox.cz \
    --cc=nikola.ciprich@linuxbox.cz \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.