From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bandan Das <bsd@redhat.com>
Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error
Date: Thu, 26 Mar 2015 17:03:21 -0400
Message-ID: <jpgoanfo4iu.fsf@redhat.com>
References: <20150325230259.GA29924@morn.localdomain>
	<CABYiri-+jWwToU4wQMFgXGQNeAZoRBuM97jLjBLAsQYJf+-fow@mail.gmail.com>
	<20150326000502.GA1217@morn.localdomain>
	<20150326155807.GA13271@potion.brq.redhat.com>
	<20150326163657.GA16305@morn.localdomain>
	<CABYiri9cVTu2jWqP2_RM3YtC4JvTW7YKS+zirPK56KKptnDa8w@mail.gmail.com>
	<20150326170654.GB16305@morn.localdomain>
	<CABYiri_D-Y8uxW30ddwomnbotCFFWLEKU7rona761W5yo66-zQ@mail.gmail.com>
	<20150326174056.GC13271@potion.brq.redhat.com>
	<CABYiri-TZp51en0cdE9k=iq3dr-eVM=+Z2vx89R81V97CgUp2Q@mail.gmail.com>
	<20150326204053.GC27093@potion.brq.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Andrey Korolyov <andrey@xdel.ru>,
	"Kevin O'Connor" <kevin@koconnor.net>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"qemu-devel\@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm\@vger.kernel.org" <kvm@vger.kernel.org>
To: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:46880 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753083AbbCZVDY convert rfc822-to-8bit (ORCPT
	<rfc822;kvm@vger.kernel.org>); Thu, 26 Mar 2015 17:03:24 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Radim Kr=C4=8Dm=C3=A1=C5=99 <rkrcmar@redhat.com> writes:

> 2015-03-26 21:24+0300, Andrey Korolyov:
>> On Thu, Mar 26, 2015 at 8:40 PM, Radim Kr=C4=8Dm=C3=A1=C5=99 <rkrcma=
r@redhat.com> wrote:
>> > 2015-03-26 20:08+0300, Andrey Korolyov:
>> >> KVM internal error. Suberror: 2
>> >> extra data[0]: 800000ef
>> >> extra data[1]: 80000b0d
>> >
>> > Btw. does this part ever change?
>> >
>> > I see that first report had:
>> >
>> >   KVM internal error. Suberror: 2
>> >   extra data[0]: 800000d1
>> >   extra data[1]: 80000b0d
>> >
>> > Was that a Windows guest by any chance?
>>=20
>> Yes, exactly, different extra data output was from a Windows VMs.
>
> Windows uses vector 0xd1 for timer interrupts.

> I second Bandan -- checking that it reproduces on other machine would=
 be
> great for sanity :)  (Although a bug in our APICv is far more likely.=
)

If it's APICv related, a run without apicv enabled could give more hint=
s.

Your "devices not getting reset" hypothesis makes the most sense to me,
maybe the timer vector in the error message is just one part of
the whole story. Another misbehaving interrupt from the dark comes in a=
t the
same time and leads to a double fault.