From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Pietsch <stefan.pietsch@lsexperts.de>
Cc: Gleb Natapov <gleb@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>,
kvm@vger.kernel.org, 707257@bugs.debian.org
Subject: Re: Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
Date: Mon, 17 Jun 2013 18:07:27 +0200 [thread overview]
Message-ID: <51BF343F.6010601@redhat.com> (raw)
In-Reply-To: <51BD05E0.5000205@sp.consulting.lsexperts.de>
Il 16/06/2013 02:25, Stefan Pietsch ha scritto:
> Bisecting leads to
>
> git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398
> git bisect good 007a3b547512d69f67ceb9641796d64552bd337e
> git bisect good 1f3141e80b149e7215313dff29e9a0c47811b1d1
> git bisect good 286da4156dc65c8a054580fdd96b7709132dce8d
> git bisect bad 25391454e73e3156202264eb3c473825afe4bc94
> git bisect good 218e763f458c44f30041c1b48b4371e130fd4317
>
>
> first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
> KVM: VMX: don't clobber segment AR of unusable segments.
>
> 25391454e73e3156202264eb3c473825afe4bc94
> emulate_invalid_guest_state=0 -> hangs and shows "KVM: entry failed"
> emulate_invalid_guest_state=1 -> hangs
>
> Please note, I had to compile some revisions with
> 3f0c3d0bb2bcc4b88b22452a7cf0073ee9a0f1e6 applied, caused by
> 9ae9febae9500a0a6f5ce29ee4b8d942b5332529.
Can you please execute "info registers" and "x/10i $pc" from the QEMU
monitor at the time of the hang, and include the output? Using
"-monitor stdio" or the new GTK+ interface can help.
Also, can you run under tracing (for information on how to do this, see
http://www.linux-kvm.org/page/Tracing) and include the bottom of the log?
Thanks,
Paolo
next prev parent reply other threads:[~2013-06-17 16:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <518A7323.7000302@sp.consulting.lsexperts.de>
[not found] ` <1368061686.4131.225.camel@deadeye.wl.decadent.org.uk>
[not found] ` <518BF14E.3070509@sp.consulting.lsexperts.de>
[not found] ` <5194C254.4000201@sp.consulting.lsexperts.de>
2013-05-19 1:00 ` Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021" Ben Hutchings
2013-05-19 12:32 ` Gleb Natapov
2013-05-29 15:05 ` Stefan Pietsch
2013-05-29 17:20 ` Ben Hutchings
2013-06-05 11:57 ` Stefan Pietsch
2013-06-05 12:10 ` Gleb Natapov
2013-06-05 12:51 ` Stefan Pietsch
2013-06-06 6:42 ` Gleb Natapov
2013-06-06 7:20 ` Gleb Natapov
2013-06-06 11:35 ` Stefan Pietsch
2013-06-06 11:40 ` Gleb Natapov
2013-06-06 12:10 ` Stefan Pietsch
2013-06-09 9:43 ` Gleb Natapov
2013-06-13 11:57 ` Stefan Pietsch
2013-06-13 13:42 ` Paolo Bonzini
2013-06-13 13:46 ` Paolo Bonzini
2013-06-13 14:59 ` Stefan Pietsch
2013-06-16 0:25 ` Stefan Pietsch
2013-06-17 16:07 ` Paolo Bonzini [this message]
2013-06-18 16:35 ` Stefan Pietsch
2013-06-19 13:41 ` Gleb Natapov
2013-06-19 14:12 ` Stefan Pietsch
2013-06-19 14:38 ` Gleb Natapov
2013-06-20 17:01 ` Stefan Pietsch
2013-06-23 7:51 ` Gleb Natapov
2013-06-23 16:51 ` Stefan Pietsch
2013-06-23 17:36 ` Gleb Natapov
2013-06-24 11:43 ` Stefan Pietsch
2013-06-24 11:47 ` Gleb Natapov
2013-06-24 11:59 ` Stefan Pietsch
2013-06-24 12:30 ` Gleb Natapov
2013-06-24 20:42 ` Stefan Pietsch
2013-06-26 10:47 ` Gleb Natapov
2013-06-27 14:09 ` Stefan Pietsch
2013-06-27 20:01 ` Gleb Natapov
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=51BF343F.6010601@redhat.com \
--to=pbonzini@redhat.com \
--cc=707257@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=stefan.pietsch@lsexperts.de \
/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.