Thomas Huth writes:
> On 28/03/2023 07.26, Markus Armbruster wrote:
>> Paolo Bonzini writes:
>>
>>> I am honestly not a fan of adding a more complex option,.just because
>>> query-command-line-options only returns the square holes whereas here we
>>> got a round one.
>>>
>>> Can we imagine anot
On 28/03/2023 07.26, Markus Armbruster wrote:
Paolo Bonzini writes:
I am honestly not a fan of adding a more complex option,.just because
query-command-line-options only returns the square holes whereas here we
got a round one.
Can we imagine another functionality that would be added to -tear
Paolo Bonzini writes:
> I am honestly not a fan of adding a more complex option,.just because
> query-command-line-options only returns the square holes whereas here we
> got a round one.
>
> Can we imagine another functionality that would be added to -teardown? If
> not, it's not a good design.
I am honestly not a fan of adding a more complex option,.just because
query-command-line-options only returns the square holes whereas here we
got a round one.
Can we imagine another functionality that would be added to -teardown? If
not, it's not a good design. If it works, I would add a complete
Add new -teardown option with an async=on|off parameter. It is visible
in the output of query-command-line-options QMP command, so it can be
discovered and used by libvirt.
The option -async-teardown is now redundant. We'd normally deprecate it
and remove it after a grace period, but it was introd
