From: Marcelo Tosatti <mtosatti@redhat.com>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: kvm@vger.kernel.org
Subject: Re: windows 2008 guest causing rcu_shed to emit NMI
Date: Fri, 25 Jan 2013 18:49:54 -0200 [thread overview]
Message-ID: <20130125204954.GA14411@amt.cnet> (raw)
In-Reply-To: <CABYiri9mJKC77R4QrBrsRD0r9CXKvmkMOBPWdhpZ06p1yB9tnQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2013-01-25 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 18:00 windows 2008 guest causing rcu_shed to emit NMI Andrey Korolyov
2013-01-24 0:52 ` Marcelo Tosatti
2013-01-24 10:54 ` Andrey Korolyov
2013-01-24 12:20 ` Marcelo Tosatti
2013-01-25 7:45 ` Andrey Korolyov
2013-01-25 20:49 ` Marcelo Tosatti [this message]
2013-01-27 21:04 ` Andrey Korolyov
[not found] ` <20130127231447.GB14721@amt.cnet>
2013-01-28 13:56 ` Andrey Korolyov
2013-01-28 23:35 ` Andrey Korolyov
[not found] ` <20130129231546.GA29904@amt.cnet>
2013-01-30 8:21 ` Andrey Korolyov
2013-01-30 20:11 ` Marcelo Tosatti
2013-01-31 17:40 ` Andrey Korolyov
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=20130125204954.GA14411@amt.cnet \
--to=mtosatti@redhat.com \
--cc=andrey@xdel.ru \
--cc=kvm@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.