Peter Krempa writes:
> On Wed, May 15, 2019 at 15:48:29 +0200, Markus Armbruster wrote:
>> Kevin Wolf writes:
>> > Am 18.04.2019 um 22:03 hat Markus Armbruster geschrieben:
>> >> Kevin Wolf writes:
>
> [...]
>
>> > Do you expect libvirt to check a full list of all QMP commands, types,
>> > etc.
On Wed, May 15, 2019 at 15:48:29 +0200, Markus Armbruster wrote:
> Kevin Wolf writes:
> > Am 18.04.2019 um 22:03 hat Markus Armbruster geschrieben:
> >> Kevin Wolf writes:
[...]
> > Do you expect libvirt to check a full list of all QMP commands, types,
> > etc. it ever uses against the schema a
Kevin Wolf writes:
> Am 18.04.2019 um 22:03 hat Markus Armbruster geschrieben:
>> Kevin Wolf writes:
>>
>> > Sometimes, the behaviour of QEMU changes compatibly, but without a
>> > change in the QMP syntax (usually by allowing values or operations that
>> > previously resulted in an error). QMP
On Wed, May 15, 2019 at 12:58:46 +0200, Kevin Wolf wrote:
> Am 18.04.2019 um 22:03 hat Markus Armbruster geschrieben:
> > Kevin Wolf writes:
> >
> > > Sometimes, the behaviour of QEMU changes compatibly, but without a
> > > change in the QMP syntax (usually by allowing values or operations that
>
Am 18.04.2019 um 22:03 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Sometimes, the behaviour of QEMU changes compatibly, but without a
> > change in the QMP syntax (usually by allowing values or operations that
> > previously resulted in an error). QMP clients may still need to k
Kevin Wolf writes:
> Sometimes, the behaviour of QEMU changes compatibly, but without a
> change in the QMP syntax (usually by allowing values or operations that
> previously resulted in an error). QMP clients may still need to know
> whether the extension is available.
>
> This allows to add a l
