From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: windows 2008 guest causing rcu_shed to emit NMI
Date: Fri, 25 Jan 2013 18:49:54 -0200
Message-ID: <20130125204954.GA14411@amt.cnet>
References: <CABYiri-CCSWvEWvrhwuVQHYq4_xa1=sJyUPfjwYLE43yC+KOaQ@mail.gmail.com>
 <20130124005226.GB5479@amt.cnet>
 <CABYiri8+tEjhN5px_iQCGDZiG5RbwBYWPxCswDL1TrpXRB4nng@mail.gmail.com>
 <20130124122045.GA28893@amt.cnet>
 <CABYiri9mJKC77R4QrBrsRD0r9CXKvmkMOBPWdhpZ06p1yB9tnQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org
To: Andrey Korolyov <andrey@xdel.ru>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:51075 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753863Ab3AYXZy (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 25 Jan 2013 18:25:54 -0500
Content-Disposition: inline
In-Reply-To: <CABYiri9mJKC77R4QrBrsRD0r9CXKvmkMOBPWdhpZ06p1yB9tnQ@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Fri, Jan 25, 2013 at 10:45:02AM +0300, Andrey Korolyov wrote:
> On Thu, Jan 24, 2013 at 4:20 PM, Marcelo Tosatti <mtosatti@redhat.com> wrote:
> > On Thu, Jan 24, 2013 at 01:54:03PM +0300, Andrey Korolyov wrote:
> >> Thank you Marcelo,
> >>
> >> Host node locking up sometimes later than yesterday, bur problem still
> >> here, please see attached dmesg. Stuck process looks like
> >> root     19251  0.0  0.0 228476 12488 ?        D    14:42   0:00
> >> /usr/bin/kvm -no-user-config -device ? -device pci-assign,? -device
> >> virtio-blk-pci,? -device
> >>
> >> on fourth vm by count.
> >>
> >> Should I try upstream kernel instead of applying patch to the latest
> >> 3.4 or it is useless?
> >
> > If you can upgrade to an upstream kernel, please do that.
> >
> 
> With vanilla 3.7.4 there is almost no changes, and NMI started firing
> again. External symptoms looks like following: starting from some
> count, may be third or sixth vm, qemu-kvm process allocating its
> memory very slowly and by jumps, 20M-200M-700M-1.6G in minutes. Patch
> helps, of course - on both patched 3.4 and vanilla 3.7 I`m able to
> kill stuck kvm processes and node returned back to the normal, when on
> 3.2 sending SIGKILL to the process causing zombies and hanged ``ps''
> output (problem and workaround when no scheduler involved described
> here http://www.spinics.net/lists/kvm/msg84799.html).

Try disabling pause loop exiting with ple_gap=0 kvm-intel.ko module parameter.