From: Markus Armbruster <armbru@redhat.com>
To: alistair23@gmail.com
Cc: qemu-devel@nongnu.org, armbru@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, peterx@redhat.com, philmd@linaro.org,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH 0/7] Fix some -device T,help crashes
Date: Thu, 12 Mar 2026 09:10:35 +0100 [thread overview]
Message-ID: <87fr65zcw4.fsf@pond.sub.org> (raw)
In-Reply-To: <20260312043158.4191378-1-alistair.francis@wdc.com> (alistair's message of "Thu, 12 Mar 2026 14:31:51 +1000")
alistair23@gmail.com writes:
> From: Alistair Francis <alistair.francis@wdc.com>
>
> Markus reported the following
>
> """
> Watch this:
>
> $ qemu-system-aarch64 -S -display none -M virt -device acpi-ged,help
> qemu-system-aarch64: ../hw/core/qdev.c:858: qdev_get_machine: Assertion `dev' failed.
The comment right before the assertion explains:
/*
* Any call to this function before machine is created is treated
* as a programming error as of now.
*/
i.e. we're talking about straightforward programming errors.
> A number of devices crash this way:
>
> * acpi-ged (aarch64 arm i386 loongarch64 x86_64)
> * fsl-imx6 (aarch64 arm)
> * fsl-imx7 (aarch64 arm)
> * fsl-imx8mp (aarch64)
> * microchip.pfsoc (riscv64)
> * riscv.sifive.e.soc (riscv32 riscv64)
> * xlnx-zynqmp (aarch64)
> """
>
> This series fixes the crashes
Series
Tested-by: Markus Armbruster <armbru@redhat.com>
prev parent reply other threads:[~2026-03-12 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 4:31 [PATCH 0/7] Fix some -device T,help crashes alistair23
2026-03-12 4:31 ` [PATCH 1/7] hw/riscv: sifive_e: Don't call qdev_get_machine in soc init alistair23
2026-03-12 9:20 ` Peter Maydell
2026-03-12 4:31 ` [PATCH 2/7] hw/riscv: microchip_pfsoc: " alistair23
2026-03-12 4:31 ` [PATCH 3/7] hw/arm: xlnx-zynqmp: " alistair23
2026-03-12 9:25 ` Peter Maydell
2026-03-12 13:39 ` BALATON Zoltan
2026-03-13 0:18 ` Alistair Francis
2026-03-16 8:04 ` Thomas Huth
2026-03-12 4:31 ` [PATCH 4/7] hw/arm: fsl-imx7: " alistair23
2026-03-12 4:31 ` [PATCH 5/7] hw/arm: fsl-imx8mp: " alistair23
2026-03-12 4:31 ` [PATCH 6/7] hw/arm: fsl-imx6: " alistair23
2026-03-12 4:31 ` [PATCH 7/7] hw/acpi: generic_event_device: " alistair23
2026-03-12 9:37 ` Thomas Huth
2026-03-12 8:10 ` Markus Armbruster [this message]
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=87fr65zcw4.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.