From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gwu.lbox.cz ([62.245.111.132]:60644 "EHLO gwu.lbox.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751047AbeBINK1 (ORCPT ); Fri, 9 Feb 2018 08:10:27 -0500 Date: Fri, 9 Feb 2018 14:10:24 +0100 From: Nikola Ciprich To: Greg KH Cc: stable@vger.kernel.org, nik@linuxbox.cz Subject: Re: 4.14.x - KVM guests crashing Message-ID: <20180209131024.GZ2270@pcnci.linuxbox.cz> References: <20180209095637.GA14309@pcnci.linuxbox.cz> <20180209130640.GC6252@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180209130640.GC6252@kroah.com> Sender: stable-owner@vger.kernel.org List-ID: Hi Greg, > > 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. OK, I'll report there, thanks. > > 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. yeah, I know. We always tend to stick to some stable kernel branch for some time.. the bad thing is it takes quite long for the crash to occur (>1day at least) so I'm keeping bisect as the last resort. I'll see if I get something from the KVM maillist and possibly report needed patches here. thanks nik > > thanks, > > greg k-h > -- ------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28.rijna 168, 709 00 Ostrava tel.: +420 591 166 214 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@linuxbox.cz -------------------------------------