From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Johannes Bauer <dfnsonfsduifb@gmx.de>, kvm@vger.kernel.org
Subject: Re: KVM entry failed, hardware error
Date: Mon, 04 Jun 2012 11:56:23 +0300 [thread overview]
Message-ID: <4FCC7837.7040508@redhat.com> (raw)
In-Reply-To: <20120604085331.GB23670@redhat.com>
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
next prev parent reply other threads:[~2012-06-04 8:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 12:18 KVM entry failed, hardware error Johannes Bauer
2012-06-03 12:33 ` Avi Kivity
2012-06-03 13:01 ` Johannes Bauer
2012-06-03 13:43 ` Avi Kivity
2012-06-03 16:25 ` Johannes Bauer
2012-06-04 8:53 ` Gleb Natapov
2012-06-04 8:56 ` Avi Kivity [this message]
2012-06-04 18:28 ` Johannes Bauer
2012-06-04 18:32 ` Johannes Bauer
2012-06-05 13:59 ` David Ahern
2012-06-06 18:19 ` Johannes Bauer
2012-06-06 15:53 ` Avi Kivity
2012-06-06 18:07 ` Johannes Bauer
2012-06-07 7:12 ` Avi Kivity
2012-06-07 10:03 ` Johannes Bauer
2012-06-07 10:54 ` Avi Kivity
2012-06-07 14:52 ` Avi Kivity
2012-06-07 15:39 ` Johannes Bauer
2012-06-07 17:25 ` Avi Kivity
2012-06-07 19:14 ` Johannes Bauer
2012-06-10 15:19 ` Avi Kivity
2012-06-12 10:23 ` Johannes Bauer
2012-06-12 10:45 ` Avi Kivity
2012-06-07 19:46 ` Johannes Bauer
2012-06-07 19:54 ` Johannes Bauer
2012-06-03 13:04 ` Johannes Bauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FCC7837.7040508@redhat.com \
--to=avi@redhat.com \
--cc=dfnsonfsduifb@gmx.de \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox