All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: -device T,help crashes
Date: Wed, 11 Mar 2026 16:14:35 +0100	[thread overview]
Message-ID: <2bdcb31f-b53b-44eb-ae70-b36e73cdad1c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_tJRFKGCFdG-x+QAwur7VuqZUqhJg_U-hKi1iym5=+Ng@mail.gmail.com>

On 11/03/2026 15.55, Peter Maydell wrote:
> On Wed, 11 Mar 2026 at 14:10, Markus Armbruster <armbru@redhat.com> wrote:
>>
>> 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.
>>
>> 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)
> 
> Largely speaking these are pretty useless to try to create on
> the command line, of course...

Agreed, but note that you can also query help for non-user-creatable devices 
normally, e.g.:

$ ./qemu-system-x86_64 -device port92
qemu-system-x86_64: -device port92: Parameter 'driver' expects a pluggable 
device type
$ ./qemu-system-x86_64 -device port92,help
port92 options:
   a20[0]=<link<irq>>
   port92[0]=<child<memory-region>>

... so we likely should fix the crashes anyway, even if we decide to mark 
the devices with user_creatable = false.

  Thomas



  reply	other threads:[~2026-03-11 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 14:09 -device T,help crashes Markus Armbruster
2026-03-11 14:55 ` Peter Maydell
2026-03-11 15:14   ` Thomas Huth [this message]
2026-03-12  8:05     ` Markus Armbruster
2026-03-11 15:16 ` BALATON Zoltan
2026-03-12  8:15 ` Markus Armbruster
2026-03-17  6:24   ` Thomas Huth
2026-03-17  7:35     ` Markus Armbruster
2026-03-17  8:12       ` Thomas Huth
2026-03-17  9:27         ` Markus Armbruster
2026-03-17  9:37           ` Thomas Huth
2026-03-17 10:30             ` Markus Armbruster

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=2bdcb31f-b53b-44eb-ae70-b36e73cdad1c@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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.