Lines Matching full:commands
17 the protocol; details of the commands and data structures can
92 Issuing Commands
120 The actual commands are documented in the :doc:`qemu-qmp-ref`.
130 the server reads and queues commands as they arrive. It executes
131 commands from the queue one after the other. Commands executed
133 possibly overtaking prior in-band commands. The client may therefore
135 commands.
137 To be able to match responses back to their commands, the client needs
138 to pass ``id`` with out-of-band commands. Passing it with all commands
141 If the client sends in-band commands faster than the server can
145 To ensure commands to be executed out-of-band get read and executed,
146 the client should have at most eight in-band commands in flight.
148 Only a few commands support out-of-band execution. The ones that do
151 Commands Responses
157 As long as the commands were issued with a proper ``id`` field, then the
238 state where it can't parse additional commands. To get it back into
340 other commands will return the ``CommandNotFound`` error. Asynchronous
348 effect, all commands (except ``qmp_capabilities``) are allowed and asynchronous
398 means upstream will never use any downstream names for its commands,
427 1. Introducing new commands is okay. If you want to extend an existing
434 3. Introducing new errors for use in new commands is okay. Adding new
435 errors to existing commands counts as extension, so 1. applies.