From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: KVM entry failed, hardware error Date: Mon, 4 Jun 2012 11:53:31 +0300 Message-ID: <20120604085331.GB23670@redhat.com> References: <4FCB55FE.2010808@gmx.de> <4FCB59A2.4020008@redhat.com> <4FCB6045.1050002@gmx.de> <4FCB69FE.80303@redhat.com> <4FCB8FFD.4020705@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , kvm@vger.kernel.org To: Johannes Bauer Return-path: Received: from mx1.redhat.com ([209.132.183.28]:30428 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756611Ab2FDIxg (ORCPT ); Mon, 4 Jun 2012 04:53:36 -0400 Content-Disposition: inline In-Reply-To: <4FCB8FFD.4020705@gmx.de> Sender: kvm-owner@vger.kernel.org List-ID: 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? -- Gleb.