From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59353) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbEaP-00034Q-74 for qemu-devel@nongnu.org; Thu, 26 Mar 2015 16:41:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YbEaM-0005wf-0q for qemu-devel@nongnu.org; Thu, 26 Mar 2015 16:41:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbEaL-0005wI-Oz for qemu-devel@nongnu.org; Thu, 26 Mar 2015 16:41:01 -0400 Date: Thu, 26 Mar 2015 21:40:54 +0100 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Message-ID: <20150326204053.GC27093@potion.brq.redhat.com> References: <20150325230259.GA29924@morn.localdomain> <20150326000502.GA1217@morn.localdomain> <20150326155807.GA13271@potion.brq.redhat.com> <20150326163657.GA16305@morn.localdomain> <20150326170654.GB16305@morn.localdomain> <20150326174056.GC13271@potion.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrey Korolyov Cc: "kvm@vger.kernel.org" , "qemu-devel@nongnu.org" , "Dr. David Alan Gilbert" , Bandan Das , Kevin O'Connor , Gerd Hoffmann , Paolo Bonzini 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 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.)