Markus Armbruster <arm...@redhat.com> writes:
> I fooled around a bit, and I think there are a few lose ends.
[...]
> Talking to a QMP monitor that supports OOB:
>
> $ socat UNIX:test-qmp READLINE,history=$HOME/.qmp_history,prompt='QMP> '
> {"QMP": {"version": {"qemu": {"micro": 50, "minor": 12, "major": 2},
> "package": "v2.12.0-1703-gb909799463"}, "capabilities": ["oob"]}}
> QMP> { "execute": "qmp_capabilities", "arguments": { "oob": true } }
> {"error": {"class": "GenericError", "desc": "Parameter 'oob' is
> unexpected"}}
> QMP> { "execute": "qmp_capabilities", "arguments": { "enable": ["oob"] } }
> {"return": {}}
> QMP> { "execute": "query-qmp-schema" }
> {"error": {"class": "GenericError", "desc": "Out-Of-Band capability
> requires that every command contains an 'id' field"}}
>
> Why does every command require 'id'?
I found one reason: event COMMAND_DROPPED wants it. Any other reason?
[...]
