From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
mengcong <mc@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [qom-next] Bisecting virtio-scsi issue
Date: Sun, 17 Jun 2012 16:28:54 +0200 [thread overview]
Message-ID: <4FDDE9A6.6020101@suse.de> (raw)
In-Reply-To: <4FDDE6A1.5050706@redhat.com>
Am 17.06.2012 16:16, schrieb Avi Kivity:
> On 06/17/2012 05:08 PM, Andreas Färber wrote:
>> Am 17.06.2012 10:37, schrieb Avi Kivity:
>>> On 06/16/2012 03:41 AM, Andreas Färber wrote:
>>>> After multiple runs of not-so-successful bisecting, it appears as if the
>>>> qom-next commit "qbus: Make child devices links" [1] is causing
>>>> assertions for both virtio-scsi and ahci but not for qemu-system-x86_64
>>>> without parameters:
>>>>
>>>> $ x86_64-softmmu/qemu-system-x86_64 -enable-kvm -device
>>>> virtio-scsi-pci,id=mcbus
>>>> qemu-system-x86_64: /home/andreas/QEMU/qemu-rcar/memory.c:1259:
>>>> memory_region_add_subregion_common: Assertion `!subregion->parent' failed.
[...]
>>> You can also run 'qemu mtree' from gdb after including scripts/qemu-gdb.py.
>
> (gdb) source /path/to/qemu/scripts/qemu-gdb.py
> (gdb) qemu mtree
(gdb) qemu mtree
0000000000000000-7ffffffffffffffe system (@ 0x5555564627b0)
0000000000000000-000000000000ffff io (@ 0x555556462880)
000000000000007e-000000000000007f kvmvapic (I/O) (@ 0x55555647c838)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-06-17 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 0:41 [Qemu-devel] [qom-next] Bisecting virtio-scsi issue Andreas Färber
2012-06-17 8:37 ` Avi Kivity
2012-06-17 14:08 ` Andreas Färber
2012-06-17 14:16 ` Avi Kivity
2012-06-17 14:28 ` Andreas Färber [this message]
2012-06-17 14:33 ` Anthony Liguori
2012-06-17 14:57 ` Avi Kivity
2012-06-17 15:16 ` Andreas Färber
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=4FDDE9A6.6020101@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=mc@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).