From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexey Korolev <alexey.korolev@endace.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [BUG] QEMU crashes when 64bit BAR is present
Date: Wed, 05 Dec 2012 08:30:32 +0100 [thread overview]
Message-ID: <50BEF818.90002@redhat.com> (raw)
In-Reply-To: <50BEA7C0.5020602@endace.com>
Hi,
> And qemu error output is:
> qemu: /home/akorolev/qemu-kvm/exec.c:2255: register_subpage: Assertion `existing->mr->subpage || existing->mr == &io_mem_unassigned' failed.
>
> Guest OS is Centos 5.5 and log is pretty boring, as qemu crashes before Linux can report an issue.
Where does it crash? seabios? linux kernel?
Still reproducable with 1.3.0?
cheers,
Gerd
next prev parent reply other threads:[~2012-12-05 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 1:47 [Qemu-devel] [BUG] QEMU crashes when 64bit BAR is present Alexey Korolev
2012-12-05 7:30 ` Gerd Hoffmann [this message]
2012-12-05 20:23 ` Alexey Korolev
2012-12-05 20:28 ` Alexey Korolev
2012-12-06 4:09 ` Alexey Korolev
2012-12-06 7:45 ` Gerd Hoffmann
2012-12-07 0:22 ` Alexey Korolev
2012-12-07 8:32 ` Gerd Hoffmann
2012-12-10 2:05 ` Alexey Korolev
2012-12-10 7:22 ` Gerd Hoffmann
2012-12-13 1:23 ` Alexey Korolev
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=50BEF818.90002@redhat.com \
--to=kraxel@redhat.com \
--cc=alexey.korolev@endace.com \
--cc=avi@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).