2014-06-05 15:45:30 +04:00
|
|
|
# -*- Mode: Python -*-
|
2020-07-29 21:50:24 +03:00
|
|
|
# vim: filetype=python
|
2017-01-13 17:41:23 +03:00
|
|
|
|
|
|
|
##
|
2017-08-24 22:14:08 +03:00
|
|
|
# = Block devices
|
2017-01-13 17:41:23 +03:00
|
|
|
##
|
2014-06-05 15:45:30 +04:00
|
|
|
|
|
|
|
{ 'include': 'block-core.json' }
|
|
|
|
|
2017-01-13 17:41:23 +03:00
|
|
|
##
|
2017-08-24 22:14:08 +03:00
|
|
|
# == Additional block stuff (VM related)
|
2017-01-13 17:41:23 +03:00
|
|
|
##
|
|
|
|
|
2014-06-05 15:45:32 +04:00
|
|
|
##
|
2015-09-25 17:03:30 +03:00
|
|
|
# @BiosAtaTranslation:
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
|
|
|
# Policy that BIOS should use to interpret cylinder/head/sector
|
|
|
|
# addresses. Note that Bochs BIOS and SeaBIOS will not actually
|
|
|
|
# translate logical CHS to physical; instead, they will use logical
|
|
|
|
# block addressing.
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @auto: If cylinder/heads/sizes are passed, choose between none and
|
|
|
|
# LBA depending on the size of the disk. If they are not passed,
|
|
|
|
# choose none if QEMU can guess that the disk had 16 or fewer
|
|
|
|
# heads, large if QEMU can guess that the disk had 131072 or fewer
|
|
|
|
# tracks across all heads (i.e. cylinders*heads<131072), otherwise
|
|
|
|
# LBA.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
|
|
|
# @none: The physical disk geometry is equal to the logical geometry.
|
|
|
|
#
|
|
|
|
# @lba: Assume 63 sectors per track and one of 16, 32, 64, 128 or 255
|
2023-04-28 13:54:29 +03:00
|
|
|
# heads (if fewer than 255 are enough to cover the whole disk with
|
|
|
|
# 1024 cylinders/head). The number of cylinders/head is then
|
|
|
|
# computed based on the number of sectors and heads.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @large: The number of cylinders per head is scaled down to 1024 by
|
|
|
|
# correspondingly scaling up the number of heads.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
|
|
|
# @rechs: Same as @large, but first convert a 16-head geometry to
|
2023-04-28 13:54:29 +03:00
|
|
|
# 15-head, by proportionally scaling up the number of
|
|
|
|
# cylinders/head.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
|
|
|
# Since: 2.0
|
|
|
|
##
|
|
|
|
{ 'enum': 'BiosAtaTranslation',
|
|
|
|
'data': ['auto', 'none', 'lba', 'large', 'rechs']}
|
|
|
|
|
2016-01-22 23:50:56 +03:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @FloppyDriveType:
|
2016-01-22 23:50:56 +03:00
|
|
|
#
|
|
|
|
# Type of Floppy drive to be emulated by the Floppy Disk Controller.
|
|
|
|
#
|
2022-05-03 10:37:36 +03:00
|
|
|
# @144: 1.44MB 3.5" drive
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2022-05-03 10:37:36 +03:00
|
|
|
# @288: 2.88MB 3.5" drive
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2022-05-03 10:37:36 +03:00
|
|
|
# @120: 1.2MB 5.25" drive
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2016-01-22 23:50:56 +03:00
|
|
|
# @none: No drive connected
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2016-01-22 23:50:56 +03:00
|
|
|
# @auto: Automatically determined by inserted media at boot
|
|
|
|
#
|
|
|
|
# Since: 2.6
|
|
|
|
##
|
|
|
|
{ 'enum': 'FloppyDriveType',
|
|
|
|
'data': ['144', '288', '120', 'none', 'auto']}
|
|
|
|
|
2018-02-28 20:47:57 +03:00
|
|
|
##
|
|
|
|
# @PRManagerInfo:
|
|
|
|
#
|
|
|
|
# Information about a persistent reservation manager
|
|
|
|
#
|
|
|
|
# @id: the identifier of the persistent reservation manager
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @connected: true if the persistent reservation manager is connected
|
|
|
|
# to the underlying storage or helper
|
2018-02-28 20:47:57 +03:00
|
|
|
#
|
|
|
|
# Since: 3.0
|
|
|
|
##
|
|
|
|
{ 'struct': 'PRManagerInfo',
|
|
|
|
'data': {'id': 'str', 'connected': 'bool'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @query-pr-managers:
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Returns a list of information about each persistent reservation
|
|
|
|
# manager.
|
2018-02-28 20:47:57 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Returns: a list of @PRManagerInfo for each persistent reservation
|
|
|
|
# manager
|
2018-02-28 20:47:57 +03:00
|
|
|
#
|
|
|
|
# Since: 3.0
|
|
|
|
##
|
|
|
|
{ 'command': 'query-pr-managers', 'returns': ['PRManagerInfo'],
|
|
|
|
'allow-preconfig': true }
|
|
|
|
|
2014-06-05 15:45:32 +04:00
|
|
|
##
|
|
|
|
# @eject:
|
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# Ejects the medium from a removable drive.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @device: Block device name
|
2016-09-20 14:38:46 +03:00
|
|
|
#
|
2020-02-13 20:56:26 +03:00
|
|
|
# @id: The name or QOM path of the guest device (since: 2.8)
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
2020-02-13 20:56:26 +03:00
|
|
|
# @force: If true, eject regardless of whether the drive is locked.
|
2023-04-28 13:54:29 +03:00
|
|
|
# If not specified, the default value is false.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# Features:
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @deprecated: Member @device is deprecated. Use @id instead.
|
|
|
|
#
|
2024-02-27 14:39:12 +03:00
|
|
|
# Errors:
|
2023-04-28 13:54:29 +03:00
|
|
|
# - If @device is not a valid block device, DeviceNotFound
|
2022-05-03 10:37:32 +03:00
|
|
|
#
|
qapi: convert "Note" sections to plain rST
We do not need a dedicated section for notes. By eliminating a specially
parsed section, these notes can be treated as normal rST paragraphs in
the new QMP reference manual, and can be placed and styled much more
flexibly.
Convert all existing "Note" and "Notes" sections to pure rST. As part of
the conversion, capitalize the first letter of each sentence and add
trailing punctuation where appropriate to ensure notes look sensible and
consistent in rendered HTML documentation. Markup is also re-aligned to
the de-facto standard of 3 spaces for directives.
Update docs/devel/qapi-code-gen.rst to reflect the new paradigm, and
update the QAPI parser to prohibit "Note" sections while suggesting a
new syntax. The exact formatting to use is a matter of taste, but a good
candidate is simply:
.. note:: lorem ipsum ...
... dolor sit amet ...
... consectetur adipiscing elit ...
... but there are other choices, too. The Sphinx readthedocs theme
offers theming for the following forms (capitalization unimportant); all
are adorned with a (!) symbol () in the title bar for rendered HTML
docs.
See
https://sphinx-rtd-theme.readthedocs.io/en/stable/demo/demo.html#admonitions
for examples of each directive/admonition in use.
These are rendered in orange:
.. Attention:: ...
.. Caution:: ...
.. WARNING:: ...
These are rendered in red:
.. DANGER:: ...
.. Error:: ...
These are rendered in green:
.. Hint:: ...
.. Important:: ...
.. Tip:: ...
These are rendered in blue:
.. Note:: ...
.. admonition:: custom title
admonition body text
This patch uses ".. note::" almost everywhere, with just two "caution"
directives. Several instances of "Notes:" have been converted to
merely ".. note::", or multiple ".. note::" where appropriate.
".. admonition:: notes" is used in a few places where we had an
ordered list of multiple notes that would not make sense as
standalone/separate admonitions. Two "Note:" following "Example:"
have been turned into ordinary paragraphs within the example.
NOTE: Because qapidoc.py does not attempt to preserve source ordering of
sections, the conversion of Notes from a "tagged section" to an
"untagged section" means that rendering order for some notes *may
change* as a result of this patch. The forthcoming qapidoc.py rewrite
strictly preserves source ordering in the rendered documentation, so
this issue will be rectified in the new generator.
Signed-off-by: John Snow <jsnow@redhat.com>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com> [for block*.json]
Message-ID: <20240626222128.406106-11-jsnow@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
[Commit message clarified slightly, period added to one more note]
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2024-06-27 01:21:16 +03:00
|
|
|
# .. note:: Ejecting a device with no media results in success.
|
2014-06-05 15:45:32 +04:00
|
|
|
#
|
2020-11-18 09:41:58 +03:00
|
|
|
# Since: 0.14
|
2016-06-23 16:08:55 +03:00
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2016-06-23 16:08:55 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "eject", "arguments": { "id": "ide1-0-1" } }
|
|
|
|
# <- { "return": {} }
|
2014-06-05 15:45:32 +04:00
|
|
|
##
|
2016-09-20 14:38:46 +03:00
|
|
|
{ 'command': 'eject',
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
'data': { '*device': { 'type': 'str', 'features': [ 'deprecated' ] },
|
2016-09-20 14:38:46 +03:00
|
|
|
'*id': 'str',
|
|
|
|
'*force': 'bool' } }
|
2014-06-05 15:45:32 +04:00
|
|
|
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
# @blockdev-open-tray:
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Opens a block device's tray. If there is a block driver state tree
|
|
|
|
# inserted as a medium, it will become inaccessible to the guest (but
|
|
|
|
# it will remain associated to the block device, so closing the tray
|
|
|
|
# will make it accessible again).
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# If the tray was already open before, this will be a no-op.
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There
|
|
|
|
# are cases in which no such event will be generated, these include:
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# - if the guest has locked the tray, @force is false and the guest
|
|
|
|
# does not respond to the eject request
|
|
|
|
# - if the BlockBackend denoted by @device does not have a guest
|
|
|
|
# device attached to it
|
2020-02-24 17:29:53 +03:00
|
|
|
# - if the guest device does not have an actual tray
|
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @device: Block device name
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @id: The name or QOM path of the guest device (since: 2.8)
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @force: if false (the default), an eject request will be sent to the
|
|
|
|
# guest if it has locked the tray (and the tray will not be opened
|
|
|
|
# immediately); if true, the tray will be opened regardless of
|
|
|
|
# whether it is locked
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# Features:
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @deprecated: Member @device is deprecated. Use @id instead.
|
|
|
|
#
|
2020-02-24 17:29:53 +03:00
|
|
|
# Since: 2.5
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-open-tray",
|
|
|
|
# "arguments": { "id": "ide0-1-0" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "timestamp": { "seconds": 1418751016,
|
|
|
|
# "microseconds": 716996 },
|
|
|
|
# "event": "DEVICE_TRAY_MOVED",
|
|
|
|
# "data": { "device": "ide1-cd0",
|
|
|
|
# "id": "ide0-1-0",
|
|
|
|
# "tray-open": true } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'blockdev-open-tray',
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
'data': { '*device': { 'type': 'str', 'features': [ 'deprecated' ] },
|
2020-02-24 17:29:53 +03:00
|
|
|
'*id': 'str',
|
|
|
|
'*force': 'bool' } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @blockdev-close-tray:
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Closes a block device's tray. If there is a block driver state tree
|
|
|
|
# associated with the block device (which is currently ejected), that
|
|
|
|
# tree will be loaded as the medium.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# If the tray was already closed before, this will be a no-op.
|
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @device: Block device name
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @id: The name or QOM path of the guest device (since: 2.8)
|
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# Features:
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @deprecated: Member @device is deprecated. Use @id instead.
|
|
|
|
#
|
2020-02-24 17:29:53 +03:00
|
|
|
# Since: 2.5
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-close-tray",
|
|
|
|
# "arguments": { "id": "ide0-1-0" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "timestamp": { "seconds": 1418751345,
|
|
|
|
# "microseconds": 272147 },
|
|
|
|
# "event": "DEVICE_TRAY_MOVED",
|
|
|
|
# "data": { "device": "ide1-cd0",
|
|
|
|
# "id": "ide0-1-0",
|
|
|
|
# "tray-open": false } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'blockdev-close-tray',
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
'data': { '*device': { 'type': 'str', 'features': [ 'deprecated' ] },
|
2020-02-24 17:29:53 +03:00
|
|
|
'*id': 'str' } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @blockdev-remove-medium:
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Removes a medium (a block driver state tree) from a block device.
|
|
|
|
# That block device's tray must currently be open (unless there is no
|
|
|
|
# attached guest device).
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# If the tray is open and there is no medium inserted, this will be a
|
|
|
|
# no-op.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @id: The name or QOM path of the guest device
|
|
|
|
#
|
|
|
|
# Since: 2.12
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-remove-medium",
|
|
|
|
# "arguments": { "id": "ide0-1-0" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "error": { "class": "GenericError",
|
|
|
|
# "desc": "Tray of device 'ide0-1-0' is not open" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-open-tray",
|
|
|
|
# "arguments": { "id": "ide0-1-0" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "timestamp": { "seconds": 1418751627,
|
|
|
|
# "microseconds": 549958 },
|
|
|
|
# "event": "DEVICE_TRAY_MOVED",
|
|
|
|
# "data": { "device": "ide1-cd0",
|
|
|
|
# "id": "ide0-1-0",
|
|
|
|
# "tray-open": true } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-remove-medium",
|
|
|
|
# "arguments": { "id": "ide0-1-0" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'blockdev-remove-medium',
|
|
|
|
'data': { 'id': 'str' } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @blockdev-insert-medium:
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Inserts a medium (a block driver state tree) into a block device.
|
|
|
|
# That block device's tray must currently be open (unless there is no
|
|
|
|
# attached guest device) and there must be no medium inserted already.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @id: The name or QOM path of the guest device
|
|
|
|
#
|
|
|
|
# @node-name: name of a node in the block driver state graph
|
|
|
|
#
|
|
|
|
# Since: 2.12
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-add",
|
|
|
|
# "arguments": {
|
|
|
|
# "node-name": "node0",
|
|
|
|
# "driver": "raw",
|
|
|
|
# "file": { "driver": "file",
|
|
|
|
# "filename": "fedora.iso" } } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-insert-medium",
|
|
|
|
# "arguments": { "id": "ide0-1-0",
|
|
|
|
# "node-name": "node0" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'blockdev-insert-medium',
|
|
|
|
'data': { 'id': 'str',
|
|
|
|
'node-name': 'str'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @BlockdevChangeReadOnlyMode:
|
|
|
|
#
|
|
|
|
# Specifies the new read-only mode of a block device subject to the
|
|
|
|
# @blockdev-change-medium command.
|
|
|
|
#
|
|
|
|
# @retain: Retains the current read-only mode
|
|
|
|
#
|
|
|
|
# @read-only: Makes the device read-only
|
|
|
|
#
|
|
|
|
# @read-write: Makes the device writable
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'enum': 'BlockdevChangeReadOnlyMode',
|
|
|
|
'data': ['retain', 'read-only', 'read-write'] }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @blockdev-change-medium:
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Changes the medium inserted into a block device by ejecting the
|
|
|
|
# current medium and loading a new image file which is inserted as the
|
|
|
|
# new medium (this command combines blockdev-open-tray,
|
|
|
|
# blockdev-remove-medium, blockdev-insert-medium and
|
|
|
|
# blockdev-close-tray).
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @device: Block device name
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @id: The name or QOM path of the guest device (since: 2.8)
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @filename: filename of the new image to be loaded
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @format: format to open the new image with (defaults to the probed
|
|
|
|
# format)
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @read-only-mode: change the read-only mode of the device; defaults
|
2023-04-28 13:54:29 +03:00
|
|
|
# to 'retain'
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @force: if false (the default), an eject request through
|
|
|
|
# blockdev-open-tray will be sent to the guest if it has locked
|
|
|
|
# the tray (and the tray will not be opened immediately); if true,
|
|
|
|
# the tray will be opened regardless of whether it is locked.
|
|
|
|
# (since 7.1)
|
2022-04-13 01:18:46 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# Features:
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
# @deprecated: Member @device is deprecated. Use @id instead.
|
|
|
|
#
|
2020-02-24 17:29:53 +03:00
|
|
|
# Since: 2.5
|
|
|
|
#
|
2024-07-17 05:13:09 +03:00
|
|
|
# .. qmp-example::
|
|
|
|
# :title: Change a removable medium
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-change-medium",
|
|
|
|
# "arguments": { "id": "ide0-1-0",
|
|
|
|
# "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
|
|
|
|
# "format": "raw" } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-07-17 05:13:09 +03:00
|
|
|
# .. qmp-example::
|
|
|
|
# :title: Load a read-only medium into a writable drive
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-change-medium",
|
|
|
|
# "arguments": { "id": "floppyA",
|
|
|
|
# "filename": "/srv/images/ro.img",
|
|
|
|
# "format": "raw",
|
|
|
|
# "read-only-mode": "retain" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "error":
|
|
|
|
# { "class": "GenericError",
|
|
|
|
# "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "blockdev-change-medium",
|
|
|
|
# "arguments": { "id": "floppyA",
|
|
|
|
# "filename": "/srv/images/ro.img",
|
|
|
|
# "format": "raw",
|
|
|
|
# "read-only-mode": "read-only" } }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'blockdev-change-medium',
|
qapi: Mark deprecated QMP parts with feature 'deprecated'
Add feature 'deprecated' to the deprecated QMP commands, so their
deprecation becomes visible in output of query-qmp-schema. Looks like
this:
{"name": "query-cpus",
"ret-type": "[164]",
"meta-type": "command",
"arg-type": "0",
---> "features": ["deprecated"]}
Management applications could conceivably use this for static
checking.
The deprecated commands are change, cpu-add, migrate-set-cache-size,
migrate_set_downtime, migrate_set_speed, query-cpus, query-events,
query-migrate-cache-size.
The deprecated command arguments are block-commit arguments @base and
@top, and block_set_io_throttle, blockdev-change-medium,
blockdev-close-tray, blockdev-open-tray, eject argument @device.
The deprecated command results are query-cpus-fast result @arch,
query-block result @dirty-bitmaps, query-named-block-nodes result
@encryption_key_missing and result @dirty-bitmaps's member @status.
Same for query-block result @inserted, which mirrors
query-named-block-nodes.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20200317115459.31821-27-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-17 14:54:51 +03:00
|
|
|
'data': { '*device': { 'type': 'str', 'features': [ 'deprecated' ] },
|
2020-02-24 17:29:53 +03:00
|
|
|
'*id': 'str',
|
|
|
|
'filename': 'str',
|
|
|
|
'*format': 'str',
|
2022-04-13 01:18:46 +03:00
|
|
|
'*force': 'bool',
|
2020-02-24 17:29:53 +03:00
|
|
|
'*read-only-mode': 'BlockdevChangeReadOnlyMode' } }
|
|
|
|
|
2014-06-18 10:43:44 +04:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @DEVICE_TRAY_MOVED:
|
2014-06-18 10:43:44 +04:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# Emitted whenever the tray of a removable device is moved by the
|
|
|
|
# guest or by HMP/QMP commands
|
2014-06-18 10:43:44 +04:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @device: Block device name. This is always present for
|
|
|
|
# compatibility reasons, but it can be empty ("") if the image
|
|
|
|
# does not have a device name associated.
|
2016-09-29 19:30:53 +03:00
|
|
|
#
|
2016-12-06 19:03:45 +03:00
|
|
|
# @id: The name or QOM path of the guest device (since 2.8)
|
2014-06-18 10:43:44 +04:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @tray-open: true if the tray has been opened or false if it has been
|
|
|
|
# closed
|
2014-06-18 10:43:44 +04:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
2016-06-23 16:57:27 +03:00
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2016-06-23 16:57:27 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "event": "DEVICE_TRAY_MOVED",
|
|
|
|
# "data": { "device": "ide1-cd0",
|
|
|
|
# "id": "/machine/unattached/device[22]",
|
|
|
|
# "tray-open": true
|
|
|
|
# },
|
|
|
|
# "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
|
2014-06-18 10:43:44 +04:00
|
|
|
##
|
|
|
|
{ 'event': 'DEVICE_TRAY_MOVED',
|
2016-09-29 19:30:53 +03:00
|
|
|
'data': { 'device': 'str', 'id': 'str', 'tray-open': 'bool' } }
|
2016-02-26 04:39:01 +03:00
|
|
|
|
2018-02-28 21:01:40 +03:00
|
|
|
##
|
|
|
|
# @PR_MANAGER_STATUS_CHANGED:
|
|
|
|
#
|
|
|
|
# Emitted whenever the connected status of a persistent reservation
|
|
|
|
# manager changes.
|
|
|
|
#
|
|
|
|
# @id: The id of the PR manager object
|
|
|
|
#
|
|
|
|
# @connected: true if the PR manager is connected to a backend
|
|
|
|
#
|
|
|
|
# Since: 3.0
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2018-02-28 21:01:40 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# <- { "event": "PR_MANAGER_STATUS_CHANGED",
|
|
|
|
# "data": { "id": "pr-helper0",
|
|
|
|
# "connected": true
|
|
|
|
# },
|
|
|
|
# "timestamp": { "seconds": 1519840375, "microseconds": 450486 } }
|
2018-02-28 21:01:40 +03:00
|
|
|
##
|
|
|
|
{ 'event': 'PR_MANAGER_STATUS_CHANGED',
|
|
|
|
'data': { 'id': 'str', 'connected': 'bool' } }
|
2020-02-24 17:29:53 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @block_set_io_throttle:
|
|
|
|
#
|
|
|
|
# Change I/O throttle limits for a block drive.
|
|
|
|
#
|
|
|
|
# Since QEMU 2.4, each device with I/O limits is member of a throttle
|
|
|
|
# group.
|
|
|
|
#
|
|
|
|
# If two or more devices are members of the same group, the limits
|
|
|
|
# will apply to the combined I/O of the whole group in a round-robin
|
2023-04-28 13:54:29 +03:00
|
|
|
# fashion. Therefore, setting new I/O limits to a device will affect
|
2020-02-24 17:29:53 +03:00
|
|
|
# the whole group.
|
|
|
|
#
|
|
|
|
# The name of the group can be specified using the 'group' parameter.
|
|
|
|
# If the parameter is unset, it is assumed to be the current group of
|
2023-04-28 13:54:29 +03:00
|
|
|
# that device. If it's not in any group yet, the name of the device
|
2020-02-24 17:29:53 +03:00
|
|
|
# will be used as the name for its group.
|
|
|
|
#
|
|
|
|
# The 'group' parameter can also be used to move a device to a
|
2023-04-28 13:54:29 +03:00
|
|
|
# different group. In this case the limits specified in the
|
|
|
|
# parameters will be applied to the new group only.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-07-29 09:52:20 +03:00
|
|
|
# I/O limits can be disabled by setting all of them to 0. In this
|
|
|
|
# case the device will be removed from its group and the rest of its
|
2023-04-28 13:54:29 +03:00
|
|
|
# members will not be affected. The 'group' parameter is ignored.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-27 14:39:12 +03:00
|
|
|
# Errors:
|
2023-04-28 13:54:29 +03:00
|
|
|
# - If @device is not a valid block device, DeviceNotFound
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "block_set_io_throttle",
|
|
|
|
# "arguments": { "id": "virtio-blk-pci0/virtio-backend",
|
|
|
|
# "bps": 0,
|
|
|
|
# "bps_rd": 0,
|
|
|
|
# "bps_wr": 0,
|
|
|
|
# "iops": 512,
|
|
|
|
# "iops_rd": 0,
|
|
|
|
# "iops_wr": 0,
|
|
|
|
# "bps_max": 0,
|
|
|
|
# "bps_rd_max": 0,
|
|
|
|
# "bps_wr_max": 0,
|
|
|
|
# "iops_max": 0,
|
|
|
|
# "iops_rd_max": 0,
|
|
|
|
# "iops_wr_max": 0,
|
|
|
|
# "bps_max_length": 0,
|
|
|
|
# "iops_size": 0 } }
|
|
|
|
# <- { "return": {} }
|
|
|
|
#
|
2024-07-17 05:13:08 +03:00
|
|
|
# .. qmp-example::
|
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "block_set_io_throttle",
|
|
|
|
# "arguments": { "id": "ide0-1-0",
|
|
|
|
# "bps": 1000000,
|
|
|
|
# "bps_rd": 0,
|
|
|
|
# "bps_wr": 0,
|
|
|
|
# "iops": 0,
|
|
|
|
# "iops_rd": 0,
|
|
|
|
# "iops_wr": 0,
|
|
|
|
# "bps_max": 8000000,
|
|
|
|
# "bps_rd_max": 0,
|
|
|
|
# "bps_wr_max": 0,
|
|
|
|
# "iops_max": 0,
|
|
|
|
# "iops_rd_max": 0,
|
|
|
|
# "iops_wr_max": 0,
|
|
|
|
# "bps_max_length": 60,
|
|
|
|
# "iops_size": 0 } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'block_set_io_throttle', 'boxed': true,
|
2020-11-03 12:37:20 +03:00
|
|
|
'data': 'BlockIOThrottle',
|
|
|
|
'allow-preconfig': true }
|
2020-02-24 17:29:53 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @block-latency-histogram-set:
|
|
|
|
#
|
|
|
|
# Manage read, write and flush latency histograms for the device.
|
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# If only @id parameter is specified, remove all present latency
|
|
|
|
# histograms for the device. Otherwise, add/reset some of (or all)
|
|
|
|
# latency histograms.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @id: The name or QOM path of the guest device.
|
|
|
|
#
|
|
|
|
# @boundaries: list of interval boundary values (see description in
|
2024-07-29 09:52:20 +03:00
|
|
|
# BlockLatencyHistogramInfo definition). If specified, all
|
|
|
|
# latency histograms are removed, and empty ones created for all
|
|
|
|
# io types with intervals corresponding to @boundaries (except for
|
|
|
|
# io types, for which specific boundaries are set through the
|
2023-04-28 13:54:29 +03:00
|
|
|
# following parameters).
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# @boundaries-read: list of interval boundary values for read latency
|
2023-04-28 13:54:29 +03:00
|
|
|
# histogram. If specified, old read latency histogram is removed,
|
|
|
|
# and empty one created with intervals corresponding to
|
|
|
|
# @boundaries-read. The parameter has higher priority then
|
|
|
|
# @boundaries.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @boundaries-write: list of interval boundary values for write
|
|
|
|
# latency histogram.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2023-07-20 10:16:09 +03:00
|
|
|
# @boundaries-zap: list of interval boundary values for zone append
|
|
|
|
# write latency histogram.
|
2023-05-08 08:19:14 +03:00
|
|
|
#
|
2023-04-28 13:54:29 +03:00
|
|
|
# @boundaries-flush: list of interval boundary values for flush
|
|
|
|
# latency histogram.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-27 14:39:12 +03:00
|
|
|
# Errors:
|
|
|
|
# - if device is not found or any boundary arrays are invalid.
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
|
|
|
# Since: 4.0
|
|
|
|
#
|
2024-07-17 05:13:10 +03:00
|
|
|
# .. qmp-example::
|
|
|
|
# :annotated:
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2024-07-17 05:13:10 +03:00
|
|
|
# Set new histograms for all io types with intervals
|
|
|
|
# [0, 10), [10, 50), [50, 100), [100, +inf)::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "block-latency-histogram-set",
|
|
|
|
# "arguments": { "id": "drive0",
|
|
|
|
# "boundaries": [10, 50, 100] } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-07-17 05:13:10 +03:00
|
|
|
# .. qmp-example::
|
|
|
|
# :annotated:
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2024-07-17 05:13:10 +03:00
|
|
|
# Set new histogram only for write, other histograms will remain
|
|
|
|
# not changed (or not created)::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "block-latency-histogram-set",
|
|
|
|
# "arguments": { "id": "drive0",
|
|
|
|
# "boundaries-write": [10, 50, 100] } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-07-17 05:13:10 +03:00
|
|
|
# .. qmp-example::
|
|
|
|
# :annotated:
|
|
|
|
#
|
|
|
|
# Set new histograms with the following intervals:
|
|
|
|
#
|
|
|
|
# - read, flush: [0, 10), [10, 50), [50, 100), [100, +inf)
|
|
|
|
# - write: [0, 1000), [1000, 5000), [5000, +inf)
|
2023-04-28 13:54:29 +03:00
|
|
|
#
|
2024-07-17 05:13:10 +03:00
|
|
|
# ::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "block-latency-histogram-set",
|
|
|
|
# "arguments": { "id": "drive0",
|
|
|
|
# "boundaries": [10, 50, 100],
|
|
|
|
# "boundaries-write": [1000, 5000] } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-07-17 05:13:09 +03:00
|
|
|
# .. qmp-example::
|
2024-07-17 05:13:10 +03:00
|
|
|
# :annotated:
|
|
|
|
#
|
|
|
|
# Remove all latency histograms::
|
2020-02-24 17:29:53 +03:00
|
|
|
#
|
2024-02-16 17:58:34 +03:00
|
|
|
# -> { "execute": "block-latency-histogram-set",
|
|
|
|
# "arguments": { "id": "drive0" } }
|
|
|
|
# <- { "return": {} }
|
2020-02-24 17:29:53 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'block-latency-histogram-set',
|
|
|
|
'data': {'id': 'str',
|
|
|
|
'*boundaries': ['uint64'],
|
|
|
|
'*boundaries-read': ['uint64'],
|
|
|
|
'*boundaries-write': ['uint64'],
|
2023-05-08 08:19:14 +03:00
|
|
|
'*boundaries-zap': ['uint64'],
|
2020-11-03 12:37:20 +03:00
|
|
|
'*boundaries-flush': ['uint64'] },
|
|
|
|
'allow-preconfig': true }
|