From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM entry failed, hardware error Date: Mon, 04 Jun 2012 11:56:23 +0300 Message-ID: <4FCC7837.7040508@redhat.com> References: <4FCB55FE.2010808@gmx.de> <4FCB59A2.4020008@redhat.com> <4FCB6045.1050002@gmx.de> <4FCB69FE.80303@redhat.com> <4FCB8FFD.4020705@gmx.de> <20120604085331.GB23670@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Johannes Bauer , kvm@vger.kernel.org To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59425 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755572Ab2FDI42 (ORCPT ); Mon, 4 Jun 2012 04:56:28 -0400 In-Reply-To: <20120604085331.GB23670@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/04/2012 11:53 AM, Gleb Natapov wrote: > On Sun, Jun 03, 2012 at 06:25:33PM +0200, Johannes Bauer wrote: >> Therefore, I've uploaded the compressed trace.dat file, so you can maybe >> have a look why the "report" tool barfs and interpret it correctly. I >> can't figure it out. The trace is here: >> >> http://spornkuller.de/trace.dat.bz2 >> > I can read this trace. Can you do "info pci" in qemu's monitor > after failure? What is your command line? Also after the failure: x/256b 0x2b0000 -- error compiling committee.c: too many arguments to function