Am 25.02.2014 09:30, schrieb Paolo Bonzini: > Il 25/02/2014 09:25, Markus Armbruster ha scritto: >>> > Haven't we already done that in the past? For example, object-add >>> > currently takes an unspecified dictionary of options, where you would >>> > have to consult QOM documentation to learn what makes sense to send. >> My question isn't about where the command details are documented, or >> even whether they are documented. It's about ABI promises, or lack >> thereof. The general promise for QMP is we treat it as stable ABI. If >> we add QMP commands to examine and manipulate QOM, doesn't that move all >> of QOM under the QMP ABI promise, unless we explicitly excempt it? > > We did already exempt it, in general. QOM is not declared stable.
Negative, QOM is stable in that properties may not change their type incompatibly. Properties may be dropped/renamed, since that is discoverable via qom-list, so it is less stable than the command line interface. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
