On 4/30/26 7:43 AM, Peter Krempa via Devel wrote:
This version adds an API 'virConnectGetIntrospection' which allows
to probe for every flag of every API at once via the introspection
XML which also informs users about supported typed parameters.
[...]
I've contemplated adding typed parameters as input for
the new API if we'd want to extend it to e.g. allow probing
supported stuff for e.g. a hypervisor version
I'm also adding a new API (virDomainAnnounceInterface()) and am
wondering about the same thing - the QEMU monitor command that it
provides access to ("self-announce") has several arguments that allow
setting the number of times to send the announce packet (GARP), the
interval between each one, etc, but they all seem like those type of
magic settings that users shouldn't mess with, and I don't want to add a
bunch of code just to document it as "There be Dragons here!! Forsooth
lest ye be slayed in the skirmish!!" (or something like that) and then
nobody ever uses it. But maybe in the future I'll be proven wrong, and
I'd hate for someone to have to add a virDomainAnnounceInterface2() API,
so...
I'm just about to hop into that part of the task, and figure I'll keep
the initial patches with just a "device" arg (and the "onion on your
belt" flags), then add an extra patch that adds the virTypedParameterPtr
to the API (with checks that nothing is put in it for now), and use that
as a place to poll for opinions.
