On Wed, Oct 07, 2026 at 01:25:46PM -0700, Pierrick Bouvier wrote:
> On 10/7/2026 4:47 AM, Yonggang Luo wrote:
> > This allows a combined binary to register machine types from all its
> > targets.
> > Consequently, QMP `query-machines` can return machine entries from every
> > target, even when `none` is selected. For example, a client can query the
> > combined machine list with:
> >
> > ```json
> > { "execute": "query-machines" }
> > ```
> >
> > The returned list includes the registered machine classes from all linked
> > targets. This is separate from selecting a machine: with `-target none`,
> > `-M virt` reports the targets that provide `virt` instead of choosing one
> > arbitrarily:
> >
> > ```text
> > qemu-system -target none -M virt
> > unsupported machine type: "virt" for target "none"
> > Available for targets:
> > aarch64
> > arm
> > ```
> >
>
> From the long conversation on a previous thread, I thought we reached
> the conclusion that if we didn't expose any ambiguous name, then -target
> option is unnecessary, or maybe I got lost on track of this thread.
>
> https://lore.kernel.org/qemu-devel/[email protected]/
>
> I'm not sure which semantic we want to have with -target none. If there
> is no ambiguous name registered, we just don't need it at all. It's a
> win-win IMHO.
Yes, if we expose unique names for every machine, then -target is then
redundant.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
