On Mon, Mar 02, 2015 at 06:19:47PM -0500, John Snow wrote: > +## Bitmap Modes > + > +* A Bitmap can be "enabled" (tracking writes, the default) or "disabled" > +(read-only, I/O is ignored.) This state is currently only changed internally > +for the purposes of migration, and otherwise remains enabled.
From a QMP API perspective this information is not relevant. The documentation is clearer without the concept of enabled/disabled. > +## Errors > + > +* In the event of an error that occurs after a backup job is successfully > + launched, either by a direct QMP command or a QMP transaction, the user > + will receive a BLOCK_JOB_COMPLETE event with a failure message. I would add BLOCK_JOB_CANCELLED just in case. When aborting a QMP transaction it's likely that the job will be cancelled and the user will not get a BLOCK_JOB_COMPLETE event.
pgp7nQKzcNbab.pgp
Description: PGP signature
