On 9/9/22 00:05, Paolo Bonzini wrote: > Il gio 8 set 2022, 15:47 Claudio Fontana <cfont...@suse.de> ha scritto: > >> On 9/8/22 11:39, Paolo Bonzini wrote: >>> Queued, thanks. >>> >>> Paolo >>> >>> >> >> Thanks. When it comes to programmatic checks about what QEMU supports in >> terms of audio, >> >> is there something that can be done with QMP? >> >> I checked the QMP manual at: >> >> >> https://qemu.readthedocs.io/en/latest/interop/qemu-qmp-ref.html#qapidoc-2948 >> >> but in the "Audio" section there is a bunch of Objects and enums defined, >> but no command to query them... >> >> Thanks, >> >> Claudio >> >> > No, there's nothing yet. > > Paolo > Interesting. What about Display (ie ui-*) ? I mean how do I figure out from, say, libvirt, everything that QEMU can do in terms of display, which drivers are actually installed?
Same for block... with the increasing modularization of QEMU we should I presume strengthen the discoverability of QEMU capabilities right? This way we can configure once, and install just what is needed to match the user requirements, or distro variant. As Markus mentioned maybe a more general solution would be to have these things as qom objects so that a qom-list-types can be used to get all 'audiodev' types, or all 'display' types, or all 'block' types and solve the problem this way? Is there a more general problem / solution that I am not seeing? Thanks, Claudio
