From: Jason Andryuk <jandryuk@gmail.com>
To: QEMU <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Anthony PERARD <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>
Subject: sysbus failed assert for xen_sysdev
Date: Mon, 22 Jun 2020 16:33:09 -0400 [thread overview]
Message-ID: <CAKf6xpuSD3NC2bLPQN75e2pR8asu9Ey1xTGxTNeCR_1MGsnPOg@mail.gmail.com> (raw)
Hi,
Running qemu devel for a Xen VM is failing an assert after the recent
"qdev: Rework how we plug into the parent bus" sysbus changes.
qemu-system-i386: hw/core/qdev.c:102: qdev_set_parent_bus: Assertion
`dc->bus_type && object_dynamic_cast(OBJECT(bus), dc->bus_type)'
failed.
dc->bus_type is "xen-sysbus" and it's the
`object_dynamic_cast(OBJECT(bus), dc->bus_type)` portion that fails
the assert. bus seems to be "main-system-bus", I think:
(gdb) p *bus
$3 = {obj = {class = 0x55555636d780, free = 0x7ffff7c40db0 <g_free>,
properties = 0x5555563f7180, ref = 3, parent = 0x5555563fe980}, parent
= 0x0, name = 0x5555563fec60 "main-system-bus", ...
The call comes from hw/xen/xen-legacy-backend.c:706
sysbus_realize_and_unref(SYS_BUS_DEVICE(xen_sysdev), &error_fatal);
Any pointers on what needs to be fixed?
Thanks,
Jason
next reply other threads:[~2020-06-22 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:33 Jason Andryuk [this message]
2020-06-22 21:17 ` sysbus failed assert for xen_sysdev Mark Cave-Ayland
2020-06-23 3:40 ` Jason Andryuk
2020-06-23 8:40 ` Markus Armbruster
2020-06-23 11:46 ` Paul Durrant
2020-06-24 3:23 ` Jason Andryuk
2020-06-24 10:29 ` Paul Durrant
2020-06-24 12:14 ` Jason Andryuk
2020-06-24 12:15 ` Paul Durrant
2020-06-23 12:56 ` Jason Andryuk
2020-06-23 13:22 ` Paul Durrant
2020-06-24 3:28 ` Jason Andryuk
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=CAKf6xpuSD3NC2bLPQN75e2pR8asu9Ey1xTGxTNeCR_1MGsnPOg@mail.gmail.com \
--to=jandryuk@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=armbru@redhat.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xenproject.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).