From: Gleb Natapov <gleb@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Dave Jones <davej@redhat.com>
Subject: Re: Guest hangs after some stress tests
Date: Thu, 17 May 2012 23:05:49 +0300 [thread overview]
Message-ID: <20120517200548.GA26391@redhat.com> (raw)
In-Reply-To: <CA+1xoqcP6tECqdwDSshXKYwDcWT9mspSWEa4z0OGQEwzFWnRvQ@mail.gmail.com>
On Thu, May 17, 2012 at 09:49:08PM +0200, Sasha Levin wrote:
> Hi all,
>
> I've observed a guest hang after putting a little stress testing on
> it. It basically hangs in ~10 secs after running several trinity
> instances inside a KVM tools guest.
>
And do you set hypervisor bit in KVM tool?
> The hang is easy to describe and reproduce:
>
> 1. No userspace exits observed
> 2. kvm_stat looks as follows (with all other fields at 0):
>
> kvm_entry 3631869 11819
> kvm_apic_accept_irq 1078688 11819
> kvm_exit 3631844 11819
>
> I've bisected it down to:
>
> 9b72d3b07dd99ac8ab2b84de5004a295af460536 is the first bad commit
> commit 9b72d3b07dd99ac8ab2b84de5004a295af460536
> Author: Gleb Natapov <gleb@redhat.com>
> Date: Mon Apr 30 14:45:49 2012 +0300
>
> KVM guest: make kvm_para_available() check hypervisor bit reading cpuid leaf
>
> This cpuid range does not exist on real HW and Intel spec says that
> "Information returned for highest basic information leaf" will be
> returned. Not very well defined.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> Signed-off-by: Avi Kivity <avi@redhat.com>
--
Gleb.
next prev parent reply other threads:[~2012-05-17 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 19:49 Guest hangs after some stress tests Sasha Levin
2012-05-17 20:05 ` Gleb Natapov [this message]
2012-05-17 20:14 ` Sasha Levin
2012-05-17 20:19 ` Gleb Natapov
2012-05-25 15:37 ` Marcelo Tosatti
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=20120517200548.GA26391@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=davej@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mtosatti@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox