From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Bharat Bhushan <bbhushan2@marvell.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: QEMU v5.2.0: object_new_with_type: assertion failed: (type != NULL)
Date: Fri, 5 Feb 2021 14:03:51 +0100 [thread overview]
Message-ID: <a9fe645c-5737-a004-a8e6-2e0f9cdf6908@redhat.com> (raw)
In-Reply-To: <DM6PR18MB2698B10216D8BD1ED5DE8809E3B29@DM6PR18MB2698.namprd18.prod.outlook.com>
On 2/5/21 12:48 PM, Bharat Bhushan wrote:
>
> Hi All,
>
> I am using QEMU version "v5.2.0" and getting below error when running on arm64
>
> $ qemu-system-aarch64 --version
>
> ERROR:../qom/object.c:711:object_new_with_type: assertion failed: (type != NULL)
> Bail out! ERROR:../qom/object.c:711:object_new_with_type: assertion failed: (type != NULL)
>
> Running GDB give below information.
> Is this something known.
>
> (gdb) run
> Starting program: /root/qemu-system-aarch64
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [New Thread 0xfffff703ed90 (LWP 5212)]
> **
> ERROR:../qom/object.c:711:object_new_with_type: assertion failed: (type != NULL)
> Bail out! ERROR:../qom/object.c:711:object_new_with_type: assertion failed: (type != NULL)
>
> Thread 1 "qemu-system-aar" received signal SIGABRT, Aborted.
> 0x0000fffff73e380c in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x0000fffff73e380c in raise () from /lib64/libc.so.6
> #1 0x0000fffff73d0bcc in abort () from /lib64/libc.so.6
> #2 0x0000fffff7b7c058 in g_assertion_message () from /lib64/libglib-2.0.so.0
> #3 0x0000fffff7b7c0b8 in g_assertion_message_expr () from /lib64/libglib-2.0.so.0
> #4 0x0000aaaaab2b880c in object_new_with_type (type=<optimized out>) at ../qom/object.c:711
> #5 0x0000aaaaab2b8870 in object_new (typename=typename@entry=0xaaaaab50a668 "container") at ../qom/object.c:744
How can you not have "container" registered? libqom is a core part
of QEMU... Cc'ing Gerd for the module initialization.
> #6 0x0000aaaaab2b9ec4 in object_get_root () at ../qom/object.c:1674
> #7 0x0000aaaaab2a4c0c in get_chardevs_root () at ../chardev/char.c:50
> #8 0x0000aaaaaaf9f2b4 in chardev_machine_done_hook (notifier=<optimized out>, unused=<optimized out>)
> at ../chardev/chardev-sysemu.c:45
> #9 0x0000aaaaab3d4ae8 in module_call_init (type=type@entry=MODULE_INIT_QOM) at ../util/module.c:106
> #10 0x0000aaaaab235000 in qemu_init (argc=1, argv=0xfffffffffcb8, envp=<optimized out>) at ../softmmu/vl.c:2916
> #11 0x0000aaaaaad9e084 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../softmmu/main.c:49
> (gdb)
>
> Thanks
> -Bharat
>
next prev parent reply other threads:[~2021-02-05 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 11:48 QEMU v5.2.0: object_new_with_type: assertion failed: (type != NULL) Bharat Bhushan
2021-02-05 13:03 ` Philippe Mathieu-Daudé [this message]
2021-02-05 15:55 ` Paolo Bonzini
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=a9fe645c-5737-a004-a8e6-2e0f9cdf6908@redhat.com \
--to=philmd@redhat.com \
--cc=bbhushan2@marvell.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--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).