From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry
 failed, hardware error 0x80000021"
Date: Wed, 19 Jun 2013 17:38:20 +0300
Message-ID: <20130619143820.GQ5832@redhat.com>
References: <51B073F1.8030107@sp.consulting.lsexperts.de>
 <20130606114025.GC4725@redhat.com>
 <51B07C3F.2060104@sp.consulting.lsexperts.de>
 <20130609094328.GM4725@redhat.com>
 <51B9B3AE.2040902@sp.consulting.lsexperts.de>
 <51B9CC54.6070009@redhat.com>
 <51B9DE49.3070606@sp.consulting.lsexperts.de>
 <51BD05E0.5000205@sp.consulting.lsexperts.de>
 <20130619134154.GN5832@redhat.com>
 <51C1BC34.6020303@sp.consulting.lsexperts.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Ben Hutchings <ben@decadent.org.uk>, kvm@vger.kernel.org,
	707257@bugs.debian.org
To: Stefan Pietsch <stefan.pietsch@lsexperts.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:65465 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756427Ab3FSOib (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 19 Jun 2013 10:38:31 -0400
Content-Disposition: inline
In-Reply-To: <51C1BC34.6020303@sp.consulting.lsexperts.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote:
> On 19.06.2013 15:41, Gleb Natapov wrote:
> > On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
> >>
> >> 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
> >>
> > With emulate_invalid_guest_state=1 the commit does nothing. Can you
> > double check that 218e763f458c44f30041c1b48b4371e130fd4317 works for you
> > with emulate_invalid_guest_state=1?
> 
> 
> 218e763f458c44f30041c1b48b4371e130fd4317
> emulate_invalid_guest_state=0 -> works
> emulate_invalid_guest_state=1 -> hangs
> 
> 25391454e73e3156202264eb3c473825afe4bc94 broke
> emulate_invalid_guest_state=0.
Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu
monitor after the hang.

--
			Gleb.