2011-07-20 00:41:55 +04:00
|
|
|
# *-*- Mode: Python -*-*
|
2020-07-29 21:50:24 +03:00
|
|
|
# vim: filetype=python
|
2011-07-20 00:41:55 +04:00
|
|
|
|
2013-03-15 22:07:51 +04:00
|
|
|
##
|
2020-09-25 19:23:06 +03:00
|
|
|
# = General note concerning the use of guest agent interfaces
|
2013-03-15 22:07:51 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# "unsupported" is a higher-level error than the errors that
|
|
|
|
# individual commands might document. The caller should always be
|
|
|
|
# prepared to receive QERR_UNSUPPORTED, even if the given command
|
|
|
|
# doesn't specify it, or doesn't document any failure mode at all.
|
2020-09-25 19:23:06 +03:00
|
|
|
##
|
|
|
|
|
|
|
|
##
|
|
|
|
# = QEMU guest agent protocol commands and structs
|
2013-03-15 22:07:51 +04:00
|
|
|
##
|
|
|
|
|
2017-03-15 15:56:51 +03:00
|
|
|
{ 'pragma': { 'doc-required': true } }
|
|
|
|
|
2022-07-27 12:21:34 +03:00
|
|
|
# Lists with items allowed to permit QAPI rule violations; think twice
|
|
|
|
# before you add to them!
|
2017-03-15 15:56:54 +03:00
|
|
|
{ 'pragma': {
|
2021-03-23 12:40:23 +03:00
|
|
|
# Types whose member names may use '_'
|
|
|
|
'member-name-exceptions': [
|
|
|
|
'GuestAgentInfo'
|
|
|
|
],
|
2017-03-15 15:56:54 +03:00
|
|
|
# Commands allowed to return a non-dictionary:
|
2021-03-23 12:40:16 +03:00
|
|
|
'command-returns-exceptions': [
|
2017-03-15 15:56:54 +03:00
|
|
|
'guest-file-open',
|
|
|
|
'guest-fsfreeze-freeze',
|
|
|
|
'guest-fsfreeze-freeze-list',
|
|
|
|
'guest-fsfreeze-status',
|
|
|
|
'guest-fsfreeze-thaw',
|
|
|
|
'guest-get-time',
|
|
|
|
'guest-set-vcpus',
|
|
|
|
'guest-sync',
|
qapi: Require member documentation (with loophole)
The QAPI generator forces you to document your stuff. Except for
command arguments, event data, and members of enum and object types:
these the generator silently "documents" as "Not documented".
We can't require proper documentation there without first fixing all
the offenders. We've always had too many offenders to pull that off.
Right now, we have more than 500. Worse, we seem to fix old ones no
faster than we add new ones: in the past year, we fixed 22 ones, but
added 26 new ones.
To help arrest the backsliding, make missing documentation an error
unless the command, type, or event is in listed in new pragma
documentation-exceptions.
List all the current offenders: 117 commands and types in qapi/, and 9
in qga/.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240205074709.3613229-7-armbru@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2024-02-05 10:47:00 +03:00
|
|
|
'guest-sync-delimited' ],
|
|
|
|
# Types and commands with undocumented members:
|
|
|
|
'documentation-exceptions': [
|
2024-02-05 10:47:02 +03:00
|
|
|
'GuestNVMeSmart' ] } }
|
2017-03-15 15:56:54 +03:00
|
|
|
|
2012-02-07 23:56:48 +04:00
|
|
|
##
|
2015-08-27 13:48:35 +03:00
|
|
|
# @guest-sync-delimited:
|
2012-02-07 23:56:48 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Echo back a unique integer value, and prepend to response a leading
|
|
|
|
# sentinel byte (0xFF) the client can check scan for.
|
2012-02-07 23:56:48 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This is used by clients talking to the guest agent over the wire to
|
|
|
|
# ensure the stream is in sync and doesn't contain stale data from
|
|
|
|
# previous client. It must be issued upon initial connection, and
|
|
|
|
# after any client-side timeouts (including timeouts on receiving a
|
|
|
|
# response to this command).
|
2012-02-07 23:56:48 +04:00
|
|
|
#
|
|
|
|
# After issuing this request, all guest agent responses should be
|
2023-04-28 13:54:28 +03:00
|
|
|
# ignored until the response containing the unique integer value the
|
|
|
|
# client passed in is returned. Receival of the 0xFF sentinel byte
|
|
|
|
# must be handled as an indication that the client's
|
|
|
|
# lexer/tokenizer/parser state should be flushed/reset in preparation
|
|
|
|
# for reliably receiving the subsequent response. As an optimization,
|
|
|
|
# clients may opt to ignore all data until a sentinel value is
|
|
|
|
# receiving to avoid unnecessary processing of stale data.
|
|
|
|
#
|
|
|
|
# Similarly, clients should also precede this *request* with a 0xFF
|
|
|
|
# byte to make sure the guest agent flushes any partially read JSON
|
|
|
|
# data from a previous client connection.
|
2012-02-07 23:56:48 +04:00
|
|
|
#
|
|
|
|
# @id: randomly generated 64-bit integer
|
|
|
|
#
|
|
|
|
# Returns: The unique integer id passed in by the client
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
2015-08-27 13:48:35 +03:00
|
|
|
##
|
2013-01-02 20:15:11 +04:00
|
|
|
{ 'command': 'guest-sync-delimited',
|
2012-02-07 23:56:48 +04:00
|
|
|
'data': { 'id': 'int' },
|
|
|
|
'returns': 'int' }
|
|
|
|
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
|
|
|
# @guest-sync:
|
|
|
|
#
|
|
|
|
# Echo back a unique integer value
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This is used by clients talking to the guest agent over the wire to
|
|
|
|
# ensure the stream is in sync and doesn't contain stale data from
|
|
|
|
# previous client. All guest agent responses should be ignored until
|
|
|
|
# the provided unique integer value is returned, and it is up to the
|
|
|
|
# client to handle stale whole or partially-delivered JSON text in
|
|
|
|
# such a way that this response can be obtained.
|
|
|
|
#
|
|
|
|
# In cases where a partial stale response was previously received by
|
|
|
|
# the client, this cannot always be done reliably. One particular
|
|
|
|
# scenario being if qemu-ga responses are fed character-by-character
|
|
|
|
# into a JSON parser. In these situations, using guest-sync-delimited
|
|
|
|
# may be optimal.
|
|
|
|
#
|
|
|
|
# For clients that fetch responses line by line and convert them to
|
|
|
|
# JSON objects, guest-sync should be sufficient, but note that in
|
|
|
|
# cases where the channel is dirty some attempts at parsing the
|
2012-02-07 23:56:48 +04:00
|
|
|
# response may result in a parser error.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Such clients should also precede this command with a 0xFF byte to
|
|
|
|
# make sure the guest agent flushes any partially read JSON data from
|
|
|
|
# a previous session.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# @id: randomly generated 64-bit integer
|
|
|
|
#
|
|
|
|
# Returns: The unique integer id passed in by the client
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2013-01-02 20:15:11 +04:00
|
|
|
{ 'command': 'guest-sync',
|
2011-07-20 00:41:55 +04:00
|
|
|
'data': { 'id': 'int' },
|
|
|
|
'returns': 'int' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-ping:
|
|
|
|
#
|
|
|
|
# Ping the guest agent, a non-error return implies success
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-ping' }
|
|
|
|
|
2013-03-05 13:39:11 +04:00
|
|
|
##
|
|
|
|
# @guest-get-time:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Get the information about guest's System Time relative to the Epoch
|
|
|
|
# of 1970-01-01 in UTC.
|
2013-03-05 13:39:11 +04:00
|
|
|
#
|
|
|
|
# Returns: Time in nanoseconds.
|
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 1.5
|
2013-03-05 13:39:11 +04:00
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-time',
|
|
|
|
'returns': 'int' }
|
|
|
|
|
2013-03-05 13:39:12 +04:00
|
|
|
##
|
|
|
|
# @guest-set-time:
|
|
|
|
#
|
|
|
|
# Set guest time.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# When a guest is paused or migrated to a file then loaded from that
|
|
|
|
# file, the guest OS has no idea that there was a big gap in the time.
|
|
|
|
# Depending on how long the gap was, NTP might not be able to
|
|
|
|
# resynchronize the guest.
|
|
|
|
#
|
|
|
|
# This command tries to set guest's System Time to the given value,
|
|
|
|
# then sets the Hardware Clock (RTC) to the current System Time. This
|
|
|
|
# will make it easier for a guest to resynchronize without waiting for
|
|
|
|
# NTP. If no @time is specified, then the time to set is read from
|
|
|
|
# RTC. However, this may not be supported on all platforms (i.e.
|
|
|
|
# Windows). If that's the case users are advised to always pass a
|
2015-01-21 14:09:50 +03:00
|
|
|
# value.
|
2013-03-05 13:39:12 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @time: time of nanoseconds, relative to the Epoch of 1970-01-01 in
|
|
|
|
# UTC.
|
2013-03-05 13:39:12 +04:00
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-time',
|
2014-01-31 14:29:51 +04:00
|
|
|
'data': { '*time': 'int' } }
|
2013-03-05 13:39:12 +04:00
|
|
|
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
2012-01-17 03:44:16 +04:00
|
|
|
# @GuestAgentCommandInfo:
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2012-01-17 03:44:16 +04:00
|
|
|
# Information about guest agent commands.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2012-01-17 03:44:16 +04:00
|
|
|
# @name: name of the command
|
|
|
|
#
|
|
|
|
# @enabled: whether command is currently enabled by guest admin
|
|
|
|
#
|
2013-10-09 06:37:26 +04:00
|
|
|
# @success-response: whether command returns a response on success
|
2023-04-28 13:54:28 +03:00
|
|
|
# (since 1.7)
|
2013-10-09 06:37:26 +04:00
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 1.1.0
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestAgentCommandInfo',
|
2013-10-09 06:37:26 +04:00
|
|
|
'data': { 'name': 'str', 'enabled': 'bool', 'success-response': 'bool' } }
|
2012-01-17 03:44:16 +04:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestAgentInfo:
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
|
|
|
# Information about guest agent.
|
|
|
|
#
|
|
|
|
# @version: guest agent version
|
|
|
|
#
|
|
|
|
# @supported_commands: Information about guest agent commands
|
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 0.15.0
|
2012-01-17 03:44:16 +04:00
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestAgentInfo',
|
2011-12-07 08:03:43 +04:00
|
|
|
'data': { 'version': 'str',
|
|
|
|
'supported_commands': ['GuestAgentCommandInfo'] } }
|
2012-01-17 03:44:16 +04:00
|
|
|
##
|
|
|
|
# @guest-info:
|
|
|
|
#
|
|
|
|
# Get some information about the guest agent.
|
|
|
|
#
|
|
|
|
# Returns: @GuestAgentInfo
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2011-07-20 00:41:55 +04:00
|
|
|
{ 'command': 'guest-info',
|
|
|
|
'returns': 'GuestAgentInfo' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-shutdown:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Initiate guest-activated shutdown. Note: this is an asynchronous
|
2012-05-14 22:25:20 +04:00
|
|
|
# shutdown request, with no guarantee of successful shutdown.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @mode: "halt", "powerdown" (default), or "reboot"
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command does NOT return a response on success. Success
|
|
|
|
# condition is indicated by the VM exiting with a zero exit status or,
|
|
|
|
# when running with --no-shutdown, by issuing the query-status QMP
|
|
|
|
# command to confirm the VM status is "shutdown".
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2012-05-08 21:24:46 +04:00
|
|
|
{ 'command': 'guest-shutdown', 'data': { '*mode': 'str' },
|
qapi: Unify type bypass and add tests
For a few QMP commands, we are forced to pass an arbitrary type
without tracking it properly in QAPI. Among the existing clients,
this unnamed type was spelled 'dict', 'visitor', and '**'; this
patch standardizes on '**', matching the documentation changes
earlier in the series.
Meanwhile, for the 'gen' key, we have been ignoring the value,
although the schema consistently used "'no'" ('success-response'
was hard-coded to checking for 'no'). But now that we can support
a literal "false" in the schema, we might as well use that rather
than ignoring the value or special-casing a random string. Note
that these are one-way switches (use of 'gen':true is not the same
as omitting 'gen'). Also, the use of '**' requires 'gen':false,
but the use of 'gen':false does not mandate the use of '**'.
There is no difference to the generated code. Add some tests on
what we'd like to guarantee, although it will take later patches
to clean up test results and actually enforce the use of a bool
parameter.
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2015-05-04 18:05:19 +03:00
|
|
|
'success-response': false }
|
2011-07-20 00:41:55 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-file-open:
|
|
|
|
#
|
|
|
|
# Open a file in the guest and retrieve a file handle for it
|
|
|
|
#
|
2016-11-17 18:54:53 +03:00
|
|
|
# @path: Full path to the file in the guest to open.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @mode: open mode, as per fopen(), "r" is the default.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: Guest file handle
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-open',
|
|
|
|
'data': { 'path': 'str', '*mode': 'str' },
|
|
|
|
'returns': 'int' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-file-close:
|
|
|
|
#
|
|
|
|
# Close an open file in the guest
|
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-close',
|
|
|
|
'data': { 'handle': 'int' } }
|
|
|
|
|
2012-01-17 03:44:16 +04:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFileRead:
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
|
|
|
# Result of guest agent file-read operation
|
|
|
|
#
|
|
|
|
# @count: number of bytes read (note: count is *before*
|
2023-04-28 13:54:28 +03:00
|
|
|
# base64-encoding is applied)
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
|
|
|
# @buf-b64: base64-encoded bytes read
|
|
|
|
#
|
|
|
|
# @eof: whether EOF was encountered during read operation.
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestFileRead',
|
2012-01-17 03:44:16 +04:00
|
|
|
'data': { 'count': 'int', 'buf-b64': 'str', 'eof': 'bool' } }
|
|
|
|
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
|
|
|
# @guest-file-read:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Read from an open file in the guest. Data will be base64-encoded.
|
2020-04-14 16:30:44 +03:00
|
|
|
# As this command is just for limited, ad-hoc debugging, such as log
|
|
|
|
# file access, the number of bytes to read is limited to 48 MB.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @count: maximum number of bytes to read (default is 4KB, maximum is
|
|
|
|
# 48MB)
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: @GuestFileRead
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-read',
|
|
|
|
'data': { 'handle': 'int', '*count': 'int' },
|
|
|
|
'returns': 'GuestFileRead' }
|
|
|
|
|
2012-01-17 03:44:16 +04:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFileWrite:
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
|
|
|
# Result of guest agent file-write operation
|
|
|
|
#
|
|
|
|
# @count: number of bytes written (note: count is actual bytes
|
2023-04-28 13:54:28 +03:00
|
|
|
# written, after base64-decoding of provided buffer)
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
|
|
|
# @eof: whether EOF was encountered during write operation.
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestFileWrite',
|
2012-01-17 03:44:16 +04:00
|
|
|
'data': { 'count': 'int', 'eof': 'bool' } }
|
|
|
|
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
|
|
|
# @guest-file-write:
|
|
|
|
#
|
|
|
|
# Write to an open file in the guest.
|
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# @buf-b64: base64-encoded string representing data to be written
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @count: bytes to write (actual bytes, after base64-decode), default
|
|
|
|
# is all content in buf-b64 buffer after base64 decoding
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: @GuestFileWrite
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-write',
|
|
|
|
'data': { 'handle': 'int', 'buf-b64': 'str', '*count': 'int' },
|
|
|
|
'returns': 'GuestFileWrite' }
|
|
|
|
|
2012-01-17 03:44:16 +04:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFileSeek:
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
|
|
|
# Result of guest agent file-seek operation
|
|
|
|
#
|
|
|
|
# @position: current file position
|
|
|
|
#
|
|
|
|
# @eof: whether EOF was encountered during file seek
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestFileSeek',
|
2012-01-17 03:44:16 +04:00
|
|
|
'data': { 'position': 'int', 'eof': 'bool' } }
|
|
|
|
|
2016-02-10 00:27:16 +03:00
|
|
|
##
|
|
|
|
# @QGASeek:
|
|
|
|
#
|
|
|
|
# Symbolic names for use in @guest-file-seek
|
|
|
|
#
|
|
|
|
# @set: Set to the specified offset (same effect as 'whence':0)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2016-02-10 00:27:16 +03:00
|
|
|
# @cur: Add offset to the current location (same effect as 'whence':1)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2016-02-10 00:27:16 +03:00
|
|
|
# @end: Add offset to the end of the file (same effect as 'whence':2)
|
|
|
|
#
|
|
|
|
# Since: 2.6
|
|
|
|
##
|
|
|
|
{ 'enum': 'QGASeek', 'data': [ 'set', 'cur', 'end' ] }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestFileWhence:
|
|
|
|
#
|
|
|
|
# Controls the meaning of offset to @guest-file-seek.
|
|
|
|
#
|
|
|
|
# @value: Integral value (0 for set, 1 for cur, 2 for end), available
|
2023-04-28 13:54:28 +03:00
|
|
|
# for historical reasons, and might differ from the host's or
|
|
|
|
# guest's SEEK_* values (since: 0.15)
|
|
|
|
#
|
2016-02-10 00:27:16 +03:00
|
|
|
# @name: Symbolic name, and preferred interface
|
|
|
|
#
|
|
|
|
# Since: 2.6
|
|
|
|
##
|
|
|
|
{ 'alternate': 'GuestFileWhence',
|
|
|
|
'data': { 'value': 'int', 'name': 'QGASeek' } }
|
|
|
|
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
|
|
|
# @guest-file-seek:
|
|
|
|
#
|
|
|
|
# Seek to a position in the file, as with fseek(), and return the
|
2023-04-28 13:54:28 +03:00
|
|
|
# current file position afterward. Also encapsulates ftell()'s
|
2015-11-25 20:37:15 +03:00
|
|
|
# functionality, with offset=0 and whence=1.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# @offset: bytes to skip over in the file stream
|
|
|
|
#
|
2016-02-10 00:27:16 +03:00
|
|
|
# @whence: Symbolic or numeric code for interpreting offset
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: @GuestFileSeek
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-seek',
|
2016-02-10 00:27:16 +03:00
|
|
|
'data': { 'handle': 'int', 'offset': 'int',
|
|
|
|
'whence': 'GuestFileWhence' },
|
2011-07-20 00:41:55 +04:00
|
|
|
'returns': 'GuestFileSeek' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-file-flush:
|
|
|
|
#
|
2022-10-30 13:59:44 +03:00
|
|
|
# Write file changes buffered in userspace to disk/kernel buffers
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-flush',
|
|
|
|
'data': { 'handle': 'int' } }
|
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFsfreezeStatus:
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2012-08-23 09:14:25 +04:00
|
|
|
# An enumeration of filesystem freeze states
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2012-01-17 03:44:16 +04:00
|
|
|
# @thawed: filesystems thawed/unfrozen
|
|
|
|
#
|
|
|
|
# @frozen: all non-network guest filesystems frozen
|
|
|
|
#
|
2011-07-20 00:41:55 +04:00
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestFsfreezeStatus',
|
2024-07-12 16:24:50 +03:00
|
|
|
'data': [ 'thawed', 'frozen' ],
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSFREEZE'] } }
|
2012-01-17 03:44:16 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-fsfreeze-status:
|
|
|
|
#
|
2023-04-25 09:42:08 +03:00
|
|
|
# Get guest fsfreeze state.
|
2012-01-17 03:44:16 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Returns: GuestFsfreezeStatus ("thawed", "frozen", etc., as defined
|
|
|
|
# below)
|
2012-01-17 03:44:16 +04: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:: This may fail to properly report the current state as a
|
|
|
|
# result of some other guest processes having issued an fs
|
|
|
|
# freeze/thaw.
|
2012-04-17 04:52:17 +04:00
|
|
|
#
|
2012-01-17 03:44:16 +04:00
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2011-07-20 00:41:55 +04:00
|
|
|
{ 'command': 'guest-fsfreeze-status',
|
2024-07-12 16:24:50 +03:00
|
|
|
'returns': 'GuestFsfreezeStatus',
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSFREEZE'] } }
|
2011-07-20 00:41:55 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-fsfreeze-freeze:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Sync and freeze all freezable, local guest filesystems. If this
|
2017-04-03 12:54:38 +03:00
|
|
|
# command succeeded, you may call @guest-fsfreeze-thaw later to
|
|
|
|
# unfreeze.
|
|
|
|
#
|
2024-02-27 14:39:19 +03:00
|
|
|
# On error, all filesystems will be thawed. If no filesystems are
|
|
|
|
# frozen as a result of this call, then @guest-fsfreeze-status will
|
|
|
|
# remain "thawed" and calling @guest-fsfreeze-thaw is not necessary.
|
|
|
|
#
|
|
|
|
# Returns: Number of file systems currently frozen.
|
|
|
|
#
|
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:: On Windows, the command is implemented with the help of a
|
|
|
|
# Volume Shadow-copy Service DLL helper. The frozen state is limited
|
|
|
|
# for up to 10 seconds by VSS.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fsfreeze-freeze',
|
2024-07-12 16:24:50 +03:00
|
|
|
'returns': 'int',
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSFREEZE'] } }
|
2011-07-20 00:41:55 +04:00
|
|
|
|
2014-07-01 01:51:27 +04:00
|
|
|
##
|
|
|
|
# @guest-fsfreeze-freeze-list:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Sync and freeze specified guest filesystems. See also
|
|
|
|
# @guest-fsfreeze-freeze.
|
2014-07-01 01:51:27 +04:00
|
|
|
#
|
2024-02-27 14:39:19 +03:00
|
|
|
# On error, all filesystems will be thawed.
|
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @mountpoints: an array of mountpoints of filesystems to be frozen.
|
2023-04-28 13:54:28 +03:00
|
|
|
# If omitted, every mounted filesystem is frozen. Invalid mount
|
|
|
|
# points are ignored.
|
2014-07-01 01:51:27 +04:00
|
|
|
#
|
2024-02-27 14:39:19 +03:00
|
|
|
# Returns: Number of file systems currently frozen.
|
2014-07-01 01:51:27 +04:00
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fsfreeze-freeze-list',
|
|
|
|
'data': { '*mountpoints': ['str'] },
|
2024-07-12 16:24:50 +03:00
|
|
|
'returns': 'int',
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSFREEZE'] } }
|
2014-07-01 01:51:27 +04:00
|
|
|
|
2011-07-20 00:41:55 +04:00
|
|
|
##
|
|
|
|
# @guest-fsfreeze-thaw:
|
|
|
|
#
|
2012-04-17 04:52:17 +04:00
|
|
|
# Unfreeze all frozen guest filesystems
|
|
|
|
#
|
|
|
|
# Returns: Number of file systems thawed by this call
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
2024-06-27 01:21:17 +03:00
|
|
|
# .. note:: If the return value does not match the previous call to
|
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
|
|
|
# guest-fsfreeze-freeze, this likely means some freezable filesystems
|
|
|
|
# were unfrozen before this call, and that the filesystem state may
|
|
|
|
# have changed before issuing this command.
|
2011-07-20 00:41:55 +04:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fsfreeze-thaw',
|
2024-07-12 16:24:50 +03:00
|
|
|
'returns': 'int',
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSFREEZE'] } }
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04:00
|
|
|
|
2015-05-11 09:58:45 +03:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFilesystemTrimResult:
|
2015-05-11 09:58:45 +03:00
|
|
|
#
|
|
|
|
# @path: path that was trimmed
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-05-11 09:58:45 +03:00
|
|
|
# @error: an error message when trim failed
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-05-11 09:58:45 +03:00
|
|
|
# @trimmed: bytes trimmed for this path
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-05-11 09:58:45 +03:00
|
|
|
# @minimum: reported effective minimum for this path
|
|
|
|
#
|
|
|
|
# Since: 2.4
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestFilesystemTrimResult',
|
|
|
|
'data': {'path': 'str',
|
2024-07-12 16:24:51 +03:00
|
|
|
'*trimmed': 'int', '*minimum': 'int', '*error': 'str'},
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSTRIM'] } }
|
2015-05-11 09:58:45 +03:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFilesystemTrimResponse:
|
2015-05-11 09:58:45 +03:00
|
|
|
#
|
|
|
|
# @paths: list of @GuestFilesystemTrimResult per path that was trimmed
|
|
|
|
#
|
|
|
|
# Since: 2.4
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestFilesystemTrimResponse',
|
2024-07-12 16:24:51 +03:00
|
|
|
'data': {'paths': ['GuestFilesystemTrimResult']},
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSTRIM'] } }
|
2015-05-11 09:58:45 +03:00
|
|
|
|
2012-06-13 09:41:28 +04:00
|
|
|
##
|
|
|
|
# @guest-fstrim:
|
|
|
|
#
|
|
|
|
# Discard (or "trim") blocks which are not in use by the filesystem.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @minimum: Minimum contiguous free range to discard, in bytes. Free
|
|
|
|
# ranges smaller than this may be ignored (this is a hint and the
|
|
|
|
# guest may not respect it). By increasing this value, the fstrim
|
|
|
|
# operation will complete more quickly for filesystems with badly
|
|
|
|
# fragmented free space, although not all blocks will be
|
|
|
|
# discarded. The default value is zero, meaning "discard every
|
|
|
|
# free block".
|
2012-06-13 09:41:28 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Returns: A @GuestFilesystemTrimResponse which contains the status of
|
|
|
|
# all trimmed paths. (since 2.4)
|
2012-06-13 09:41:28 +04:00
|
|
|
#
|
|
|
|
# Since: 1.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fstrim',
|
2015-05-11 09:58:45 +03:00
|
|
|
'data': { '*minimum': 'int' },
|
2024-07-12 16:24:51 +03:00
|
|
|
'returns': 'GuestFilesystemTrimResponse',
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'CONFIG_FSTRIM'] } }
|
2012-06-13 09:41:28 +04:00
|
|
|
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @guest-suspend-disk:
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04:00
|
|
|
#
|
|
|
|
# Suspend guest to disk.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command attempts to suspend the guest using three strategies,
|
|
|
|
# in this order:
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04:00
|
|
|
#
|
2018-11-13 19:55:39 +03:00
|
|
|
# - systemd hibernate
|
|
|
|
# - pm-utils (via pm-hibernate)
|
|
|
|
# - manual write into sysfs
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command does NOT return a response on success. There is a high
|
|
|
|
# chance the command succeeded if the VM exits with a zero exit status
|
|
|
|
# or, when running with --no-shutdown, by issuing the query-status QMP
|
|
|
|
# command to to confirm the VM status is "shutdown". However, the VM
|
|
|
|
# could also exit (or set its status to "shutdown") due to other
|
|
|
|
# reasons.
|
2012-05-08 21:24:47 +04:00
|
|
|
#
|
2024-02-27 14:39:16 +03:00
|
|
|
# Errors:
|
|
|
|
# - If suspend to disk is not supported, Unsupported
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04: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:: It's strongly recommended to issue the guest-sync command
|
|
|
|
# before sending commands when the guest resumes.
|
qemu-ga: add guest-suspend-disk
As the command name implies, this command suspends the guest to disk.
The suspend operation is implemented by two functions: bios_supports_mode()
and guest_suspend(). Both functions are generic enough to be used by
other suspend modes (introduced by next commits).
Both functions will try to use the scripts provided by the pm-utils
package if it's available. If it's not available, a manual method,
which consists of directly writing to '/sys/power/state', will be used.
To reap terminated children, a new signal handler is installed in the
parent to catch SIGCHLD signals and a non-blocking call to waitpid()
is done to collect their exit statuses. The statuses, however, are
discarded.
The approach used to query the guest for suspend support deserves some
explanation. It's implemented by bios_supports_mode() and shown below:
qemu-ga
|
create pipe
|
fork()
-----------------
| |
| |
| fork()
| --------------------------
| | |
| | |
| | exec('pm-is-supported')
| |
| wait()
| write exit status to pipe
| exit
|
read pipe
This might look complex, but the resulting code is quite simple.
The purpose of that approach is to allow qemu-ga to reap its children
(semi-)automatically from its SIGCHLD handler.
Implementing this the obvious way, that's, doing the exec() call from
the first child process, would force us to introduce a more complex way
to reap qemu-ga's children. Like registering PIDs to be reaped and
having a way to wait for them when returning their exit status to
qemu-ga is necessary. The approach explained above avoids that complexity.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
2012-02-28 18:03:03 +04:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
2024-07-12 16:24:46 +03:00
|
|
|
{ 'command': 'guest-suspend-disk', 'success-response': false,
|
|
|
|
'if': { 'any': ['CONFIG_LINUX', 'CONFIG_WIN32'] } }
|
2012-02-28 18:03:04 +04:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @guest-suspend-ram:
|
2012-02-28 18:03:04 +04:00
|
|
|
#
|
|
|
|
# Suspend guest to ram.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command attempts to suspend the guest using three strategies,
|
|
|
|
# in this order:
|
2012-02-28 18:03:04 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# - systemd hibernate
|
|
|
|
# - pm-utils (via pm-hibernate)
|
2018-11-13 19:55:39 +03:00
|
|
|
# - manual write into sysfs
|
2012-02-28 18:03:04 +04:00
|
|
|
#
|
2018-12-05 22:47:00 +03:00
|
|
|
# IMPORTANT: guest-suspend-ram requires working wakeup support in
|
|
|
|
# QEMU. You should check QMP command query-current-machine returns
|
2023-04-28 13:54:28 +03:00
|
|
|
# wakeup-suspend-support: true before issuing this command. Failure
|
|
|
|
# in doing so can result in a suspended guest that QEMU will not be
|
|
|
|
# able to awaken, forcing the user to power cycle the guest to bring
|
|
|
|
# it back.
|
2012-02-28 18:03:04 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command does NOT return a response on success. There are two
|
|
|
|
# options to check for success:
|
2020-02-13 20:56:23 +03:00
|
|
|
#
|
|
|
|
# 1. Wait for the SUSPEND QMP event from QEMU
|
|
|
|
# 2. Issue the query-status QMP command to confirm the VM status is
|
|
|
|
# "suspended"
|
2012-05-08 21:24:48 +04:00
|
|
|
#
|
2024-02-27 14:39:16 +03:00
|
|
|
# Errors:
|
|
|
|
# - If suspend to ram is not supported, Unsupported
|
2012-02-28 18:03:04 +04: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:: It's strongly recommended to issue the guest-sync command
|
|
|
|
# before sending commands when the guest resumes.
|
2012-02-28 18:03:04 +04:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
2024-07-12 16:24:46 +03:00
|
|
|
{ 'command': 'guest-suspend-ram', 'success-response': false,
|
|
|
|
'if': { 'any': ['CONFIG_LINUX', 'CONFIG_WIN32'] } }
|
2012-02-28 18:03:05 +04:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @guest-suspend-hybrid:
|
2012-02-28 18:03:05 +04:00
|
|
|
#
|
|
|
|
# Save guest state to disk and suspend to ram.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command attempts to suspend the guest by executing, in this
|
|
|
|
# order:
|
2018-11-13 19:55:39 +03:00
|
|
|
#
|
|
|
|
# - systemd hybrid-sleep
|
|
|
|
# - pm-utils (via pm-suspend-hybrid)
|
2012-02-28 18:03:05 +04:00
|
|
|
#
|
2018-12-05 22:47:00 +03:00
|
|
|
# IMPORTANT: guest-suspend-hybrid requires working wakeup support in
|
|
|
|
# QEMU. You should check QMP command query-current-machine returns
|
2023-04-28 13:54:28 +03:00
|
|
|
# wakeup-suspend-support: true before issuing this command. Failure
|
|
|
|
# in doing so can result in a suspended guest that QEMU will not be
|
|
|
|
# able to awaken, forcing the user to power cycle the guest to bring
|
|
|
|
# it back.
|
2012-02-28 18:03:05 +04:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# This command does NOT return a response on success. There are two
|
|
|
|
# options to check for success:
|
2020-02-13 20:56:23 +03:00
|
|
|
#
|
|
|
|
# 1. Wait for the SUSPEND QMP event from QEMU
|
|
|
|
# 2. Issue the query-status QMP command to confirm the VM status is
|
|
|
|
# "suspended"
|
2012-05-08 21:24:49 +04:00
|
|
|
#
|
2024-02-27 14:39:16 +03:00
|
|
|
# Errors:
|
|
|
|
# - If hybrid suspend is not supported, Unsupported
|
2012-02-28 18:03:05 +04: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:: It's strongly recommended to issue the guest-sync command
|
|
|
|
# before sending commands when the guest resumes.
|
2012-02-28 18:03:05 +04:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
2024-07-12 16:24:45 +03:00
|
|
|
{ 'command': 'guest-suspend-hybrid', 'success-response': false,
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2012-02-29 20:02:23 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestIpAddressType:
|
|
|
|
#
|
|
|
|
# An enumeration of supported IP address types
|
|
|
|
#
|
|
|
|
# @ipv4: IP version 4
|
|
|
|
#
|
|
|
|
# @ipv6: IP version 6
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestIpAddressType',
|
2024-07-12 16:24:47 +03:00
|
|
|
'data': [ 'ipv4', 'ipv6' ],
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_GETIFADDRS'] } }
|
2012-02-29 20:02:23 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestIpAddress:
|
|
|
|
#
|
|
|
|
# @ip-address: IP address
|
|
|
|
#
|
|
|
|
# @ip-address-type: Type of @ip-address (e.g. ipv4, ipv6)
|
|
|
|
#
|
|
|
|
# @prefix: Network prefix length of @ip-address
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestIpAddress',
|
2012-02-29 20:02:23 +04:00
|
|
|
'data': {'ip-address': 'str',
|
|
|
|
'ip-address-type': 'GuestIpAddressType',
|
2024-07-12 16:24:47 +03:00
|
|
|
'prefix': 'int'},
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_GETIFADDRS'] } }
|
2012-02-29 20:02:23 +04:00
|
|
|
|
2017-09-12 11:54:26 +03:00
|
|
|
##
|
|
|
|
# @GuestNetworkInterfaceStat:
|
|
|
|
#
|
|
|
|
# @rx-bytes: total bytes received
|
|
|
|
#
|
|
|
|
# @rx-packets: total packets received
|
|
|
|
#
|
|
|
|
# @rx-errs: bad packets received
|
|
|
|
#
|
|
|
|
# @rx-dropped: receiver dropped packets
|
|
|
|
#
|
|
|
|
# @tx-bytes: total bytes transmitted
|
|
|
|
#
|
|
|
|
# @tx-packets: total packets transmitted
|
|
|
|
#
|
|
|
|
# @tx-errs: packet transmit problems
|
|
|
|
#
|
|
|
|
# @tx-dropped: dropped packets transmitted
|
|
|
|
#
|
|
|
|
# Since: 2.11
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestNetworkInterfaceStat',
|
|
|
|
'data': {'rx-bytes': 'uint64',
|
|
|
|
'rx-packets': 'uint64',
|
|
|
|
'rx-errs': 'uint64',
|
|
|
|
'rx-dropped': 'uint64',
|
|
|
|
'tx-bytes': 'uint64',
|
|
|
|
'tx-packets': 'uint64',
|
|
|
|
'tx-errs': 'uint64',
|
|
|
|
'tx-dropped': 'uint64'
|
2024-07-12 16:24:47 +03:00
|
|
|
},
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_GETIFADDRS'] } }
|
2017-09-12 11:54:26 +03:00
|
|
|
|
2012-02-29 20:02:23 +04:00
|
|
|
##
|
|
|
|
# @GuestNetworkInterface:
|
|
|
|
#
|
|
|
|
# @name: The name of interface for which info are being delivered
|
|
|
|
#
|
|
|
|
# @hardware-address: Hardware address of @name
|
|
|
|
#
|
|
|
|
# @ip-addresses: List of addresses assigned to @name
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @statistics: various statistic counters related to @name (since
|
|
|
|
# 2.11)
|
2017-09-12 11:54:26 +03:00
|
|
|
#
|
2012-02-29 20:02:23 +04:00
|
|
|
# Since: 1.1
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestNetworkInterface',
|
2012-02-29 20:02:23 +04:00
|
|
|
'data': {'name': 'str',
|
|
|
|
'*hardware-address': 'str',
|
2017-09-12 11:54:26 +03:00
|
|
|
'*ip-addresses': ['GuestIpAddress'],
|
2024-07-12 16:24:47 +03:00
|
|
|
'*statistics': 'GuestNetworkInterfaceStat' },
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_GETIFADDRS'] } }
|
2012-02-29 20:02:23 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-network-get-interfaces:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Get list of guest IP addresses, MAC addresses and netmasks.
|
2012-02-29 20:02:23 +04:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: List of GuestNetworkInterface
|
2012-02-29 20:02:23 +04:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-network-get-interfaces',
|
2024-07-12 16:24:47 +03:00
|
|
|
'returns': ['GuestNetworkInterface'],
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_GETIFADDRS'] } }
|
2013-03-07 01:59:29 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestLogicalProcessor:
|
|
|
|
#
|
|
|
|
# @logical-id: Arbitrary guest-specific unique identifier of the VCPU.
|
|
|
|
#
|
|
|
|
# @online: Whether the VCPU is enabled.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @can-offline: Whether offlining the VCPU is possible. This member
|
|
|
|
# is always filled in by the guest agent when the structure is
|
|
|
|
# returned, and always ignored on input (hence it can be omitted
|
|
|
|
# then).
|
2013-03-07 01:59:29 +04:00
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestLogicalProcessor',
|
2013-03-07 01:59:29 +04:00
|
|
|
'data': {'logical-id': 'int',
|
|
|
|
'online': 'bool',
|
2024-07-12 16:24:46 +03:00
|
|
|
'*can-offline': 'bool'},
|
|
|
|
'if': { 'any': ['CONFIG_LINUX', 'CONFIG_WIN32'] } }
|
2013-03-07 01:59:29 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-vcpus:
|
|
|
|
#
|
|
|
|
# Retrieve the list of the guest's logical processors.
|
|
|
|
#
|
|
|
|
# This is a read-only operation.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Returns: The list of all VCPUs the guest knows about. Each VCPU is
|
|
|
|
# put on the list exactly once, but their order is unspecified.
|
2013-03-07 01:59:29 +04:00
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-vcpus',
|
2024-07-12 16:24:46 +03:00
|
|
|
'returns': ['GuestLogicalProcessor'],
|
|
|
|
'if': { 'any': ['CONFIG_LINUX', 'CONFIG_WIN32'] } }
|
2013-03-07 01:59:29 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-set-vcpus:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Attempt to reconfigure (currently: enable/disable) logical
|
|
|
|
# processors inside the guest.
|
|
|
|
#
|
2024-02-05 10:47:02 +03:00
|
|
|
# @vcpus: The logical processors to be reconfigured. This list is
|
|
|
|
# processed node by node in order. In each node @logical-id is
|
|
|
|
# used to look up the guest VCPU, for which @online specifies the
|
|
|
|
# requested state. The set of distinct @logical-id's is only
|
|
|
|
# required to be a subset of the guest-supported identifiers.
|
|
|
|
# There's no restriction on list length or on repeating the same
|
|
|
|
# @logical-id (with possibly different @online field). Preferably
|
|
|
|
# the input list should describe a modified subset of
|
|
|
|
# @guest-get-vcpus' return value.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# Returns: The length of the initial sublist that has been
|
|
|
|
# successfully processed. The guest agent maximizes this value.
|
|
|
|
# Possible cases:
|
|
|
|
#
|
|
|
|
# - 0:
|
|
|
|
# if the @vcpus list was empty on input. Guest state has not
|
|
|
|
# been changed. Otherwise,
|
|
|
|
# - < length(@vcpus):
|
|
|
|
# more than zero initial nodes have been processed, but not the
|
|
|
|
# entire @vcpus list. Guest state has changed accordingly. To
|
|
|
|
# retrieve the error (assuming it persists), repeat the call
|
|
|
|
# with the successfully processed initial sublist removed.
|
|
|
|
# Otherwise,
|
|
|
|
# - length(@vcpus):
|
|
|
|
# call successful.
|
2013-03-07 01:59:29 +04:00
|
|
|
#
|
2024-02-27 14:39:16 +03:00
|
|
|
# Errors:
|
|
|
|
# - If the reconfiguration of the first node in @vcpus failed.
|
|
|
|
# Guest state has not been changed.
|
|
|
|
#
|
2013-03-07 01:59:29 +04:00
|
|
|
# Since: 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-vcpus',
|
|
|
|
'data': {'vcpus': ['GuestLogicalProcessor'] },
|
2024-07-12 16:24:45 +03:00
|
|
|
'returns': 'int',
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestDiskBusType:
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
#
|
|
|
|
# An enumeration of bus type of disks
|
|
|
|
#
|
|
|
|
# @ide: IDE disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @fdc: floppy disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @scsi: SCSI disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @virtio: virtio disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @xen: Xen disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @usb: USB disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @uml: UML disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @sata: SATA disks
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @sd: SD cards
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @unknown: Unknown bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @ieee1394: Win IEEE 1394 bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @ssa: Win SSA bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @fibre: Win fiber channel bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @raid: Win RAID bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @iscsi: Win iScsi bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @sas: Win serial-attaches SCSI bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @mmc: Win multimedia card (MMC) bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2015-06-30 13:25:22 +03:00
|
|
|
# @virtual: Win virtual bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-02-13 20:56:21 +03:00
|
|
|
# @file-backed-virtual: Win file-backed bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Introduce NVMe disk bus type
Assigning a NVMe disk by VFIO or emulating a NVMe controller by QEMU,
a NVMe disk get exposed in guest side. Support NVMe disk bus type and
implement posix version.
Test PCI passthrough case:
~#virsh qemu-agent-command buster '{"execute":"guest-get-disks"}' | jq
...
{
"name": "/dev/nvme0n1",
"dependencies": [],
"partition": false,
"address": {
"serial": "SAMSUNG MZQL23T8HCLS-00A07_S64HNE0N500076",
"bus-type": "nvme",
"bus": 0,
"unit": 0,
"pci-controller": {
"bus": 0,
"slot": 22,
"domain": 0,
"function": 0
},
"dev": "/dev/nvme0n1",
"target": 0
}
...
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
Message-Id: <20220420022610.418052-2-pizhenwei@bytedance.com>
2022-04-20 05:26:09 +03:00
|
|
|
# @nvme: NVMe disks (since 7.1)
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
#
|
2015-07-21 15:25:08 +03:00
|
|
|
# Since: 2.2; 'Unknown' and all entries below since 2.4
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
##
|
|
|
|
{ 'enum': 'GuestDiskBusType',
|
|
|
|
'data': [ 'ide', 'fdc', 'scsi', 'virtio', 'xen', 'usb', 'uml', 'sata',
|
2015-06-30 13:25:22 +03:00
|
|
|
'sd', 'unknown', 'ieee1394', 'ssa', 'fibre', 'raid', 'iscsi',
|
2024-07-12 16:24:48 +03:00
|
|
|
'sas', 'mmc', 'virtual', 'file-backed-virtual', 'nvme' ],
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX' ] } }
|
2015-06-30 13:25:22 +03:00
|
|
|
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestPCIAddress:
|
|
|
|
#
|
|
|
|
# @domain: domain id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @bus: bus id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @slot: slot id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @function: function id
|
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestPCIAddress',
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
'data': {'domain': 'int', 'bus': 'int',
|
2024-07-12 16:24:48 +03:00
|
|
|
'slot': 'int', 'function': 'int'},
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX' ] } }
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
|
2020-11-27 11:23:53 +03:00
|
|
|
##
|
|
|
|
# @GuestCCWAddress:
|
|
|
|
#
|
|
|
|
# @cssid: channel subsystem image id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-11-27 11:23:53 +03:00
|
|
|
# @ssid: subchannel set id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-11-27 11:23:53 +03:00
|
|
|
# @subchno: subchannel number
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-11-27 11:23:53 +03:00
|
|
|
# @devno: device number
|
|
|
|
#
|
|
|
|
# Since: 6.0
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestCCWAddress',
|
|
|
|
'data': {'cssid': 'int',
|
|
|
|
'ssid': 'int',
|
|
|
|
'subchno': 'int',
|
2024-07-12 16:24:48 +03:00
|
|
|
'devno': 'int'},
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX' ] } }
|
2020-11-27 11:23:53 +03:00
|
|
|
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
##
|
|
|
|
# @GuestDiskAddress:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @pci-controller: controller's PCI address (fields are set to -1 if
|
|
|
|
# invalid)
|
|
|
|
#
|
2016-11-17 18:54:53 +03:00
|
|
|
# @bus-type: bus type
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @bus: bus id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @target: target id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @unit: unit id
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2018-10-23 14:23:11 +03:00
|
|
|
# @serial: serial number (since: 3.1)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2018-10-23 14:23:12 +03:00
|
|
|
# @dev: device node (POSIX) or device UNC (Windows) (since: 3.1)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-11-27 11:23:53 +03:00
|
|
|
# @ccw-address: CCW address on s390x (since: 6.0)
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestDiskAddress',
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
'data': {'pci-controller': 'GuestPCIAddress',
|
|
|
|
'bus-type': 'GuestDiskBusType',
|
2018-10-23 14:23:11 +03:00
|
|
|
'bus': 'int', 'target': 'int', 'unit': 'int',
|
2020-11-27 11:23:53 +03:00
|
|
|
'*serial': 'str', '*dev': 'str',
|
2024-07-12 16:24:48 +03:00
|
|
|
'*ccw-address': 'GuestCCWAddress'},
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX' ] } }
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
|
2022-04-20 05:26:10 +03:00
|
|
|
##
|
|
|
|
# @GuestNVMeSmart:
|
|
|
|
#
|
2023-04-20 22:55:41 +03:00
|
|
|
# NVMe smart information, based on NVMe specification, section
|
2023-04-28 13:54:28 +03:00
|
|
|
# <SMART / Health Information (Log Identifier 02h)>
|
2022-04-20 05:26:10 +03:00
|
|
|
#
|
2024-02-05 10:47:03 +03:00
|
|
|
# TODO: document members briefly
|
|
|
|
#
|
2022-04-20 05:26:10 +03:00
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestNVMeSmart',
|
|
|
|
'data': {'critical-warning': 'int',
|
|
|
|
'temperature': 'int',
|
|
|
|
'available-spare': 'int',
|
|
|
|
'available-spare-threshold': 'int',
|
|
|
|
'percentage-used': 'int',
|
|
|
|
'data-units-read-lo': 'uint64',
|
|
|
|
'data-units-read-hi': 'uint64',
|
|
|
|
'data-units-written-lo': 'uint64',
|
|
|
|
'data-units-written-hi': 'uint64',
|
|
|
|
'host-read-commands-lo': 'uint64',
|
|
|
|
'host-read-commands-hi': 'uint64',
|
|
|
|
'host-write-commands-lo': 'uint64',
|
|
|
|
'host-write-commands-hi': 'uint64',
|
|
|
|
'controller-busy-time-lo': 'uint64',
|
|
|
|
'controller-busy-time-hi': 'uint64',
|
|
|
|
'power-cycles-lo': 'uint64',
|
|
|
|
'power-cycles-hi': 'uint64',
|
|
|
|
'power-on-hours-lo': 'uint64',
|
|
|
|
'power-on-hours-hi': 'uint64',
|
|
|
|
'unsafe-shutdowns-lo': 'uint64',
|
|
|
|
'unsafe-shutdowns-hi': 'uint64',
|
|
|
|
'media-errors-lo': 'uint64',
|
|
|
|
'media-errors-hi': 'uint64',
|
|
|
|
'number-of-error-log-entries-lo': 'uint64',
|
2024-07-12 16:24:48 +03:00
|
|
|
'number-of-error-log-entries-hi': 'uint64' },
|
2024-07-12 16:24:52 +03:00
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LIBUDEV' ] } }
|
2022-04-20 05:26:10 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestDiskSmart:
|
|
|
|
#
|
|
|
|
# Disk type related smart information.
|
|
|
|
#
|
2024-02-05 10:47:03 +03:00
|
|
|
# @type: disk bus type
|
2022-04-20 05:26:10 +03:00
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'union': 'GuestDiskSmart',
|
|
|
|
'base': { 'type': 'GuestDiskBusType' },
|
|
|
|
'discriminator': 'type',
|
2024-07-12 16:24:48 +03:00
|
|
|
'data': { 'nvme': 'GuestNVMeSmart' },
|
2024-07-12 16:24:52 +03:00
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LIBUDEV' ] } }
|
2022-04-20 05:26:10 +03:00
|
|
|
|
2020-10-12 11:36:01 +03:00
|
|
|
##
|
|
|
|
# @GuestDiskInfo:
|
|
|
|
#
|
|
|
|
# @name: device node (Linux) or device UNC (Windows)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-10-12 11:36:01 +03:00
|
|
|
# @partition: whether this is a partition or disk
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @dependencies: list of device dependencies; e.g. for LVs of the LVM
|
|
|
|
# this will hold the list of PVs, for LUKS encrypted volume this
|
|
|
|
# will contain the disk where the volume is placed. (Linux)
|
|
|
|
#
|
2020-10-12 11:36:01 +03:00
|
|
|
# @address: disk address information (only for non-virtual devices)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @alias: optional alias assigned to the disk, on Linux this is a name
|
|
|
|
# assigned by device mapper
|
|
|
|
#
|
2022-04-20 05:26:10 +03:00
|
|
|
# @smart: disk smart information (Since 7.1)
|
2020-10-12 11:36:01 +03:00
|
|
|
#
|
2022-04-22 16:28:07 +03:00
|
|
|
# Since: 5.2
|
2020-10-12 11:36:01 +03:00
|
|
|
##
|
|
|
|
{ 'struct': 'GuestDiskInfo',
|
2020-11-13 20:18:14 +03:00
|
|
|
'data': {'name': 'str', 'partition': 'bool', '*dependencies': ['str'],
|
2022-04-20 05:26:10 +03:00
|
|
|
'*address': 'GuestDiskAddress', '*alias': 'str',
|
2024-07-12 16:24:48 +03:00
|
|
|
'*smart': 'GuestDiskSmart'},
|
2024-07-12 16:24:52 +03:00
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LIBUDEV' ] } }
|
2020-10-12 11:36:01 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-disks:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Returns: The list of disks in the guest. For Windows these are only
|
|
|
|
# the physical disks. On Linux these are all root block devices
|
|
|
|
# of non-zero size including e.g. removable devices, loop devices,
|
|
|
|
# NBD, etc.
|
2020-10-12 11:36:01 +03:00
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-disks',
|
2024-07-12 16:24:48 +03:00
|
|
|
'returns': ['GuestDiskInfo'],
|
2024-07-12 16:24:52 +03:00
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LIBUDEV' ] } }
|
2020-10-12 11:36:01 +03:00
|
|
|
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestFilesystemInfo:
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
#
|
|
|
|
# @name: disk name
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @mountpoint: mount point path
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
# @type: file system type string
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2018-06-14 11:06:06 +03:00
|
|
|
# @used-bytes: file system used bytes (since 3.0)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2024-03-20 19:16:42 +03:00
|
|
|
# @total-bytes: filesystem capacity in bytes for unprivileged users (since 3.0)
|
|
|
|
#
|
|
|
|
# @total-bytes-privileged: filesystem capacity in bytes for privileged users
|
|
|
|
# (since 9.1)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @disk: an array of disk hardware information that the volume lies
|
|
|
|
# on, which may be empty if the disk type is not supported
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestFilesystemInfo',
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
'data': {'name': 'str', 'mountpoint': 'str', 'type': 'str',
|
2018-06-14 11:06:06 +03:00
|
|
|
'*used-bytes': 'uint64', '*total-bytes': 'uint64',
|
2024-07-12 16:24:48 +03:00
|
|
|
'*total-bytes-privileged': 'uint64', 'disk': ['GuestDiskAddress']},
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX' ] } }
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-fsinfo:
|
|
|
|
#
|
|
|
|
# Returns: The list of filesystems information mounted in the guest.
|
2023-04-28 13:54:28 +03:00
|
|
|
# The returned mountpoints may be specified to
|
|
|
|
# @guest-fsfreeze-freeze-list. Network filesystems (such as CIFS
|
|
|
|
# and NFS) are not listed.
|
qga: Add guest-get-fsinfo command
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can resolve the disk backends.
For example, when `lsblk' result is:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 1G 0 disk
`-sdb1 8:17 0 1024M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
sdc 8:32 0 1G 0 disk
`-sdc1 8:33 0 512M 0 part
`-vg0-lv0 253:1 0 1.4G 0 lvm /mnt/test
vda 252:0 0 25G 0 disk
`-vda1 252:1 0 25G 0 part /
where sdb is a SCSI disk with PCI controller 0000:00:0a.0 and ID=1,
sdc is an IDE disk with PCI controller 0000:00:01.1, and
vda is a virtio-blk disk with PCI device 0000:00:06.0,
guest-get-fsinfo command will return the following result:
{"return":
[{"name":"dm-1",
"mountpoint":"/mnt/test",
"disk":[
{"bus-type":"scsi","bus":0,"unit":1,"target":0,
"pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
{"bus-type":"ide","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
"type":"xfs"},
{"name":"vda1", "mountpoint":"/",
"disk":[
{"bus-type":"virtio","bus":0,"unit":0,"target":0,
"pci-controller":{"bus":0,"slot":6,"domain":0,"function":0}}],
"type":"ext4"}]}
In Linux guest, the disk information is resolved from sysfs. So far,
it only supports virtio-blk, virtio-scsi, IDE, SATA, SCSI disks on x86
hosts, and "disk" parameter may be empty for unsupported disk types.
Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
*updated schema to report 2.2 as initial supported version
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2014-07-01 01:51:34 +04:00
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-fsinfo',
|
2024-07-12 16:24:48 +03:00
|
|
|
'returns': ['GuestFilesystemInfo'],
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX' ] } }
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @guest-set-user-password:
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
#
|
|
|
|
# @username: the user account whose password to change
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
# @password: the new password entry string, base64 encoded
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
# @crypted: true if password is already crypt()d, false if raw
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# If the @crypted flag is true, it is the caller's responsibility to
|
|
|
|
# ensure the correct crypt() encryption scheme is used. This command
|
|
|
|
# does not attempt to interpret or report on the encryption scheme.
|
|
|
|
# Refer to the documentation of the guest operating system in question
|
|
|
|
# to determine what is supported.
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Not all guest operating systems will support use of the @crypted
|
|
|
|
# flag, as they may require the clear-text password
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
#
|
|
|
|
# The @password parameter must always be base64 encoded before
|
2023-04-28 13:54:28 +03:00
|
|
|
# transmission, even if already crypt()d, to ensure it is 8-bit safe
|
|
|
|
# when passed as JSON.
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 2.3
|
qga: add guest-set-user-password command
Add a new 'guest-set-user-password' command for changing the password
of guest OS user accounts. This command is needed to enable OpenStack
to support its API for changing the admin password of guests running
on KVM/QEMU. It is not practical to provide a command at the QEMU
level explicitly targetting administrator account password change
only, since different guest OS have different names for the admin
account. While UNIX systems use 'root', Windows systems typically
use 'Administrator' and even that can be renamed. Higher level apps
like OpenStack have the ability to figure out the correct admin
account name since they have info that QEMU/libvirt do not.
The command accepts either the clear text password string, encoded
in base64 to make it 8-bit safe in JSON:
$ echo -n "123456" | base64
MTIzNDU2
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": false,
"username": "root",
"password": "MTIzNDU2" } }'
{"return":{}}
Or a password that has already been run though a crypt(3) like
algorithm appropriate for the guest, again then base64 encoded:
$ echo -n '$6$n01A2Tau$e...snip...DfMOP7of9AJ1I8q0' | base64
JDYkb...snip...YT2Ey
$ virsh -c qemu:///system qemu-agent-command f21x86_64 \
'{ "execute": "guest-set-user-password",
"arguments": { "crypted": true,
"username": "root",
"password": "JDYkb...snip...YT2Ey" } }'
NB windows support is desirable, but not implemented in this
patch.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2015-02-11 14:26:12 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-user-password',
|
2024-07-12 16:24:54 +03:00
|
|
|
'data': { 'username': 'str', 'password': 'str', 'crypted': 'bool' },
|
|
|
|
'if': { 'any': [ 'CONFIG_WIN32', 'CONFIG_LINUX', 'CONFIG_FREEBSD'] } }
|
2015-01-22 05:40:02 +03:00
|
|
|
|
2016-11-17 18:54:51 +03:00
|
|
|
##
|
2015-01-22 05:40:02 +03:00
|
|
|
# @GuestMemoryBlock:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @phys-index: Arbitrary guest-specific unique identifier of the
|
|
|
|
# MEMORY BLOCK.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# @online: Whether the MEMORY BLOCK is enabled in guest.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @can-offline: Whether offlining the MEMORY BLOCK is possible. This
|
|
|
|
# member is always filled in by the guest agent when the structure
|
|
|
|
# is returned, and always ignored on input (hence it can be
|
|
|
|
# omitted then).
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestMemoryBlock',
|
2015-01-22 05:40:02 +03:00
|
|
|
'data': {'phys-index': 'uint64',
|
|
|
|
'online': 'bool',
|
2024-07-12 16:24:45 +03:00
|
|
|
'*can-offline': 'bool'},
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2015-01-22 05:40:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-memory-blocks:
|
|
|
|
#
|
|
|
|
# Retrieve the list of the guest's memory blocks.
|
|
|
|
#
|
|
|
|
# This is a read-only operation.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Returns: The list of all memory blocks the guest knows about. Each
|
|
|
|
# memory block is put on the list exactly once, but their order is
|
|
|
|
# unspecified.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-memory-blocks',
|
2024-07-12 16:24:45 +03:00
|
|
|
'returns': ['GuestMemoryBlock'],
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2015-01-22 05:40:02 +03:00
|
|
|
|
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @GuestMemoryBlockResponseType:
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# An enumeration of memory block operation result.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @success: the operation of online/offline memory block is
|
|
|
|
# successful.
|
|
|
|
#
|
|
|
|
# @not-found: can't find the corresponding memoryXXX directory in
|
|
|
|
# sysfs.
|
|
|
|
#
|
2015-01-22 05:40:02 +03:00
|
|
|
# @operation-not-supported: for some old kernels, it does not support
|
2023-04-28 13:54:28 +03:00
|
|
|
# online or offline memory block.
|
|
|
|
#
|
|
|
|
# @operation-failed: the operation of online/offline memory block
|
|
|
|
# fails, because of some errors happen.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestMemoryBlockResponseType',
|
|
|
|
'data': ['success', 'not-found', 'operation-not-supported',
|
2024-07-12 16:24:45 +03:00
|
|
|
'operation-failed'],
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2015-01-22 05:40:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestMemoryBlockResponse:
|
|
|
|
#
|
|
|
|
# @phys-index: same with the 'phys-index' member of @GuestMemoryBlock.
|
|
|
|
#
|
|
|
|
# @response: the result of memory block operation.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @error-code: the error number. When memory block operation fails,
|
|
|
|
# we assign the value of 'errno' to this member, it indicates what
|
|
|
|
# goes wrong. When the operation succeeds, it will be omitted.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestMemoryBlockResponse',
|
2015-01-22 05:40:02 +03:00
|
|
|
'data': { 'phys-index': 'uint64',
|
|
|
|
'response': 'GuestMemoryBlockResponseType',
|
2024-07-12 16:24:45 +03:00
|
|
|
'*error-code': 'int' },
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX'}
|
2015-01-22 05:40:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-set-memory-blocks:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Attempt to reconfigure (currently: enable/disable) state of memory
|
|
|
|
# blocks inside the guest.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
2024-02-05 10:47:01 +03:00
|
|
|
# @mem-blks: The memory blocks to be reconfigured. This list is
|
|
|
|
# processed node by node in order. In each node @phys-index is
|
|
|
|
# used to look up the guest MEMORY BLOCK, for which @online
|
|
|
|
# specifies the requested state. The set of distinct
|
|
|
|
# @phys-index's is only required to be a subset of the
|
|
|
|
# guest-supported identifiers. There's no restriction on list
|
|
|
|
# length or on repeating the same @phys-index (with possibly
|
|
|
|
# different @online field). Preferably the input list should
|
|
|
|
# describe a modified subset of @guest-get-memory-blocks' return
|
|
|
|
# value.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Returns: The operation results, it is a list of
|
|
|
|
# @GuestMemoryBlockResponse, which is corresponding to the input
|
|
|
|
# list.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
2024-02-27 14:39:20 +03:00
|
|
|
# Note: it will return an empty list if the @mem-blks list was
|
|
|
|
# empty on input, or there is an error, and in this case, guest
|
|
|
|
# state will not be changed.
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-memory-blocks',
|
|
|
|
'data': {'mem-blks': ['GuestMemoryBlock'] },
|
2024-07-12 16:24:45 +03:00
|
|
|
'returns': ['GuestMemoryBlockResponse'],
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2015-01-22 05:40:02 +03:00
|
|
|
|
2016-11-17 18:54:51 +03:00
|
|
|
##
|
2015-01-22 05:40:02 +03:00
|
|
|
# @GuestMemoryBlockInfo:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @size: the size (in bytes) of the guest memory blocks, which are the
|
|
|
|
# minimal units of memory block online/offline operations (also
|
|
|
|
# called Logical Memory Hotplug).
|
2015-01-22 05:40:02 +03:00
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
2015-05-04 18:05:27 +03:00
|
|
|
{ 'struct': 'GuestMemoryBlockInfo',
|
2024-07-12 16:24:45 +03:00
|
|
|
'data': {'size': 'uint64'},
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2015-01-22 05:40:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-memory-block-info:
|
|
|
|
#
|
|
|
|
# Get information relating to guest memory blocks.
|
|
|
|
#
|
|
|
|
# Returns: @GuestMemoryBlockInfo
|
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 2.3
|
2015-01-22 05:40:02 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-memory-block-info',
|
2024-07-12 16:24:45 +03:00
|
|
|
'returns': 'GuestMemoryBlockInfo',
|
2024-07-12 16:24:46 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2015-10-13 18:41:20 +03:00
|
|
|
|
2016-11-17 18:54:51 +03:00
|
|
|
##
|
2015-10-13 18:41:20 +03:00
|
|
|
# @GuestExecStatus:
|
|
|
|
#
|
|
|
|
# @exited: true if process has already terminated.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @exitcode: process exit code if it was normally terminated.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @signal: signal number (linux) or unhandled exception code (windows)
|
|
|
|
# if the process was abnormally terminated.
|
|
|
|
#
|
2024-03-22 17:09:10 +03:00
|
|
|
# @out-data: base64-encoded stdout of the process. This field will
|
|
|
|
# only be populated after the process exits.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2024-03-22 17:09:10 +03:00
|
|
|
# @err-data: base64-encoded stderr of the process. Note: @out-data
|
|
|
|
# and @err-data are present only if 'capture-output' was specified
|
|
|
|
# for 'guest-exec'. This field will only be populated after the
|
|
|
|
# process exits.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @out-truncated: true if stdout was not fully captured due to size
|
|
|
|
# limitation.
|
|
|
|
#
|
|
|
|
# @err-truncated: true if stderr was not fully captured due to size
|
|
|
|
# limitation.
|
2015-10-13 18:41:20 +03:00
|
|
|
#
|
|
|
|
# Since: 2.5
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestExecStatus',
|
|
|
|
'data': { 'exited': 'bool', '*exitcode': 'int', '*signal': 'int',
|
2015-10-13 18:41:23 +03:00
|
|
|
'*out-data': 'str', '*err-data': 'str',
|
|
|
|
'*out-truncated': 'bool', '*err-truncated': 'bool' }}
|
2015-10-13 18:41:20 +03:00
|
|
|
##
|
2016-11-17 18:54:55 +03:00
|
|
|
# @guest-exec-status:
|
2015-10-13 18:41:20 +03:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Check status of process associated with PID retrieved via
|
|
|
|
# guest-exec. Reap the process and associated metadata if it has
|
|
|
|
# exited.
|
2015-10-13 18:41:20 +03:00
|
|
|
#
|
|
|
|
# @pid: pid returned from guest-exec
|
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: GuestExecStatus
|
2015-10-13 18:41:20 +03:00
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 2.5
|
2015-10-13 18:41:20 +03:00
|
|
|
##
|
|
|
|
{ 'command': 'guest-exec-status',
|
|
|
|
'data': { 'pid': 'int' },
|
|
|
|
'returns': 'GuestExecStatus' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestExec:
|
2021-09-30 23:57:07 +03:00
|
|
|
#
|
2015-10-13 18:41:20 +03:00
|
|
|
# @pid: pid of child process in guest OS
|
|
|
|
#
|
2016-11-17 18:54:55 +03:00
|
|
|
# Since: 2.5
|
2015-10-13 18:41:20 +03:00
|
|
|
##
|
|
|
|
{ 'struct': 'GuestExec',
|
|
|
|
'data': { 'pid': 'int'} }
|
|
|
|
|
2023-03-23 03:19:26 +03:00
|
|
|
##
|
|
|
|
# @GuestExecCaptureOutputMode:
|
|
|
|
#
|
|
|
|
# An enumeration of guest-exec capture modes.
|
|
|
|
#
|
|
|
|
# @none: do not capture any output
|
2024-03-22 17:09:10 +03:00
|
|
|
#
|
2023-03-23 03:19:26 +03:00
|
|
|
# @stdout: only capture stdout
|
2024-03-22 17:09:10 +03:00
|
|
|
#
|
2023-03-23 03:19:26 +03:00
|
|
|
# @stderr: only capture stderr
|
2024-03-22 17:09:10 +03:00
|
|
|
#
|
2023-03-23 03:19:26 +03:00
|
|
|
# @separated: capture both stdout and stderr, but separated into
|
2024-03-22 17:09:10 +03:00
|
|
|
# GuestExecStatus out-data and err-data, respectively
|
|
|
|
#
|
|
|
|
# @merged: capture both stdout and stderr, but merge together into
|
|
|
|
# out-data. Not effective on windows guests.
|
2023-03-23 03:19:26 +03:00
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestExecCaptureOutputMode',
|
2023-03-23 03:19:27 +03:00
|
|
|
'data': [ 'none', 'stdout', 'stderr', 'separated',
|
|
|
|
{ 'name': 'merged', 'if': { 'not': 'CONFIG_WIN32' } } ] }
|
2023-03-23 03:19:26 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestExecCaptureOutput:
|
|
|
|
#
|
|
|
|
# Controls what guest-exec output gets captures.
|
|
|
|
#
|
2024-03-22 17:09:10 +03:00
|
|
|
# @flag: captures both stdout and stderr if true. Equivalent to
|
|
|
|
# GuestExecCaptureOutputMode::all. (since 2.5)
|
|
|
|
#
|
2023-03-23 03:19:26 +03:00
|
|
|
# @mode: capture mode; preferred interface
|
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
|
|
|
{ 'alternate': 'GuestExecCaptureOutput',
|
|
|
|
'data': { 'flag': 'bool',
|
|
|
|
'mode': 'GuestExecCaptureOutputMode'} }
|
|
|
|
|
2015-10-13 18:41:20 +03:00
|
|
|
##
|
|
|
|
# @guest-exec:
|
|
|
|
#
|
|
|
|
# Execute a command in the guest
|
|
|
|
#
|
|
|
|
# @path: path or executable name to execute
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @arg: argument list to pass to executable
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @env: environment variables to pass to executable
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2017-03-15 15:57:06 +03:00
|
|
|
# @input-data: data to be passed to process stdin (base64 encoded)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @capture-output: bool flag to enable capture of stdout/stderr of
|
2024-03-22 17:09:10 +03:00
|
|
|
# running process. Defaults to false.
|
2015-10-13 18:41:20 +03:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: PID
|
2015-10-13 18:41:20 +03:00
|
|
|
#
|
|
|
|
# Since: 2.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-exec',
|
|
|
|
'data': { 'path': 'str', '*arg': ['str'], '*env': ['str'],
|
2023-03-23 03:19:26 +03:00
|
|
|
'*input-data': 'str', '*capture-output': 'GuestExecCaptureOutput' },
|
2015-10-13 18:41:20 +03:00
|
|
|
'returns': 'GuestExec' }
|
2017-04-04 09:46:31 +03:00
|
|
|
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestHostName:
|
2021-09-30 23:57:07 +03:00
|
|
|
#
|
2017-04-04 09:46:31 +03:00
|
|
|
# @host-name: Fully qualified domain name of the guest OS
|
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestHostName',
|
|
|
|
'data': { 'host-name': 'str' } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-host-name:
|
|
|
|
#
|
|
|
|
# Return a name for the machine.
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# The returned name is not necessarily a fully-qualified domain name,
|
|
|
|
# or even present in DNS or some other name service at all. It need
|
|
|
|
# not even be unique on your local network or site, but usually it is.
|
2017-04-04 09:46:31 +03:00
|
|
|
#
|
2024-02-27 14:39:18 +03:00
|
|
|
# Returns: the host name of the machine
|
2017-04-04 09:46:31 +03:00
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-host-name',
|
|
|
|
'returns': 'GuestHostName' }
|
2017-04-19 12:26:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestUser:
|
2021-09-30 23:57:07 +03:00
|
|
|
#
|
2020-02-13 20:56:22 +03:00
|
|
|
# @user: Username
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-02-13 20:56:22 +03:00
|
|
|
# @domain: Logon domain (windows only)
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @login-time: Time of login of this user on the computer. If
|
|
|
|
# multiple instances of the user are logged in, the earliest login
|
|
|
|
# time is reported. The value is in fractional seconds since
|
|
|
|
# epoch time.
|
2017-04-19 12:26:15 +03:00
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestUser',
|
2024-07-12 16:24:53 +03:00
|
|
|
'data': { 'user': 'str', 'login-time': 'number', '*domain': 'str' },
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_UTMPX' ] } }
|
2017-04-19 12:26:15 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-users:
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2017-04-19 12:26:15 +03:00
|
|
|
# Retrieves a list of currently active users on the VM.
|
|
|
|
#
|
|
|
|
# Returns: A unique list of users.
|
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-users',
|
2024-07-12 16:24:53 +03:00
|
|
|
'returns': ['GuestUser'],
|
|
|
|
'if': { 'any': ['CONFIG_WIN32', 'HAVE_UTMPX' ] } }
|
2017-04-19 13:52:58 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestTimezone:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @zone: Timezone name. These values may differ depending on guest/OS
|
|
|
|
# and should only be used for informational purposes.
|
|
|
|
#
|
|
|
|
# @offset: Offset to UTC in seconds, negative numbers for time zones
|
|
|
|
# west of GMT, positive numbers for east
|
2017-04-19 13:52:58 +03:00
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestTimezone',
|
|
|
|
'data': { '*zone': 'str', 'offset': 'int' } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-timezone:
|
|
|
|
#
|
|
|
|
# Retrieves the timezone information from the guest.
|
|
|
|
#
|
|
|
|
# Returns: A GuestTimezone dictionary.
|
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-timezone',
|
|
|
|
'returns': 'GuestTimezone' }
|
2017-07-14 17:28:56 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestOSInfo:
|
|
|
|
#
|
|
|
|
# @kernel-release:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: release field returned by uname(2)
|
|
|
|
# * Windows: build number of the OS
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @kernel-version:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: version field returned by uname(2)
|
|
|
|
# * Windows: version number of the OS
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @machine:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: machine field returned by uname(2)
|
|
|
|
# * Windows: one of x86, x86_64, arm, ia64
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @id:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: contains string "mswindows"
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @name:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: contains string "Microsoft Windows"
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @pretty-name:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: product name, e.g. "Microsoft Windows 10 Enterprise"
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @version:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: long version string, e.g. "Microsoft Windows Server
|
|
|
|
# 2008"
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @version-id:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: short version identifier, e.g. "7" or "20012r2"
|
|
|
|
#
|
2017-07-14 17:28:56 +03:00
|
|
|
# @variant:
|
2023-04-28 13:54:28 +03:00
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: contains string "server" or "client"
|
2017-07-14 17:28:56 +03:00
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @variant-id:
|
|
|
|
# * POSIX: as defined by os-release(5)
|
|
|
|
# * Windows: contains string "server" or "client"
|
2017-07-14 17:28:56 +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:: On POSIX systems the fields @id, @name, @pretty-name,
|
|
|
|
# @version, @version-id, @variant and @variant-id follow the
|
|
|
|
# definition specified in os-release(5). Refer to the manual page for
|
|
|
|
# exact description of the fields. Their values are taken from the
|
|
|
|
# os-release file. If the file is not present in the system, or the
|
|
|
|
# values are not present in the file, the fields are not included.
|
2017-07-14 17:28:56 +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
|
|
|
# On Windows the values are filled from information gathered from
|
|
|
|
# the system.
|
2017-07-14 17:28:56 +03:00
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestOSInfo',
|
|
|
|
'data': {
|
|
|
|
'*kernel-release': 'str', '*kernel-version': 'str',
|
|
|
|
'*machine': 'str', '*id': 'str', '*name': 'str',
|
|
|
|
'*pretty-name': 'str', '*version': 'str', '*version-id': 'str',
|
|
|
|
'*variant': 'str', '*variant-id': 'str' } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-osinfo:
|
|
|
|
#
|
|
|
|
# Retrieve guest operating system information
|
|
|
|
#
|
|
|
|
# Returns: @GuestOSInfo
|
|
|
|
#
|
|
|
|
# Since: 2.10
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-osinfo',
|
|
|
|
'returns': 'GuestOSInfo' }
|
2020-07-21 18:40:41 +03:00
|
|
|
|
2020-10-21 10:15:20 +03:00
|
|
|
##
|
|
|
|
# @GuestDeviceType:
|
2024-02-05 10:47:03 +03:00
|
|
|
#
|
|
|
|
# @pci: PCI device
|
2020-10-21 10:15:20 +03:00
|
|
|
##
|
|
|
|
{ 'enum': 'GuestDeviceType',
|
2024-07-12 16:24:49 +03:00
|
|
|
'data': [ 'pci' ],
|
|
|
|
'if': 'CONFIG_WIN32' }
|
2020-10-21 10:15:20 +03:00
|
|
|
|
2020-07-21 18:40:41 +03:00
|
|
|
##
|
2020-10-21 10:15:17 +03:00
|
|
|
# @GuestDeviceIdPCI:
|
2020-07-21 18:40:41 +03:00
|
|
|
#
|
|
|
|
# @vendor-id: vendor ID
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-07-21 18:40:41 +03:00
|
|
|
# @device-id: device ID
|
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
2020-10-21 10:15:17 +03:00
|
|
|
{ 'struct': 'GuestDeviceIdPCI',
|
2024-07-12 16:24:49 +03:00
|
|
|
'data': { 'vendor-id': 'uint16', 'device-id': 'uint16' },
|
|
|
|
'if': 'CONFIG_WIN32' }
|
2020-07-21 18:40:41 +03:00
|
|
|
|
|
|
|
##
|
2020-10-21 10:15:17 +03:00
|
|
|
# @GuestDeviceId:
|
2020-07-21 18:40:41 +03:00
|
|
|
#
|
2024-02-05 10:47:03 +03:00
|
|
|
# Id of the device
|
|
|
|
#
|
|
|
|
# @type: device type
|
2020-07-21 18:40:41 +03:00
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
2020-10-21 10:15:17 +03:00
|
|
|
{ 'union': 'GuestDeviceId',
|
2020-10-21 10:15:20 +03:00
|
|
|
'base': { 'type': 'GuestDeviceType' },
|
|
|
|
'discriminator': 'type',
|
2024-07-12 16:24:49 +03:00
|
|
|
'data': { 'pci': 'GuestDeviceIdPCI' },
|
|
|
|
'if': 'CONFIG_WIN32' }
|
2020-07-21 18:40:41 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestDeviceInfo:
|
|
|
|
#
|
|
|
|
# @driver-name: name of the associated driver
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-10-21 10:15:18 +03:00
|
|
|
# @driver-date: driver release date, in nanoseconds since the epoch
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-07-21 18:40:41 +03:00
|
|
|
# @driver-version: driver version
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2020-10-21 10:15:17 +03:00
|
|
|
# @id: device ID
|
2020-07-21 18:40:41 +03:00
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestDeviceInfo',
|
|
|
|
'data': {
|
|
|
|
'driver-name': 'str',
|
2020-10-21 10:15:18 +03:00
|
|
|
'*driver-date': 'int',
|
2020-07-21 18:40:41 +03:00
|
|
|
'*driver-version': 'str',
|
2020-10-21 10:15:17 +03:00
|
|
|
'*id': 'GuestDeviceId'
|
2024-07-12 16:24:49 +03:00
|
|
|
},
|
|
|
|
'if': 'CONFIG_WIN32' }
|
2020-07-21 18:40:41 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-devices:
|
|
|
|
#
|
|
|
|
# Retrieve information about device drivers in Windows guest
|
|
|
|
#
|
|
|
|
# Returns: @GuestDeviceInfo
|
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-devices',
|
2024-07-12 16:24:49 +03:00
|
|
|
'returns': ['GuestDeviceInfo'],
|
|
|
|
'if': 'CONFIG_WIN32' }
|
2020-10-20 11:12:52 +03:00
|
|
|
|
2020-10-20 11:12:57 +03:00
|
|
|
##
|
|
|
|
# @GuestAuthorizedKeys:
|
|
|
|
#
|
|
|
|
# @keys: public keys (in OpenSSH/sshd(8) authorized_keys format)
|
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestAuthorizedKeys',
|
|
|
|
'data': {
|
|
|
|
'keys': ['str']
|
2024-04-24 17:40:29 +03:00
|
|
|
}
|
|
|
|
}
|
2020-10-20 11:12:57 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-ssh-get-authorized-keys:
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# Return the public keys from user .ssh/authorized_keys on Unix
|
|
|
|
# systems (not implemented for other systems).
|
2020-10-20 11:12:57 +03:00
|
|
|
#
|
2024-01-29 14:50:08 +03:00
|
|
|
# @username: the user account to add the authorized keys
|
|
|
|
#
|
2020-10-20 11:12:57 +03:00
|
|
|
# Returns: @GuestAuthorizedKeys
|
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-ssh-get-authorized-keys',
|
|
|
|
'data': { 'username': 'str' },
|
2024-04-24 17:40:29 +03:00
|
|
|
'returns': 'GuestAuthorizedKeys'
|
|
|
|
}
|
2020-10-20 11:12:57 +03:00
|
|
|
|
2020-10-20 11:12:52 +03:00
|
|
|
##
|
|
|
|
# @guest-ssh-add-authorized-keys:
|
|
|
|
#
|
2024-01-29 14:50:08 +03:00
|
|
|
# Append public keys to user .ssh/authorized_keys on Unix systems (not
|
|
|
|
# implemented for other systems).
|
|
|
|
#
|
2020-10-20 11:12:52 +03:00
|
|
|
# @username: the user account to add the authorized keys
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
|
|
|
# @keys: the public keys to add (in OpenSSH/sshd(8) authorized_keys
|
|
|
|
# format)
|
|
|
|
#
|
2020-11-03 05:01:44 +03:00
|
|
|
# @reset: ignore the existing content, set it with the given keys only
|
2020-10-20 11:12:52 +03:00
|
|
|
#
|
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-ssh-add-authorized-keys',
|
2024-04-24 17:40:29 +03:00
|
|
|
'data': { 'username': 'str', 'keys': ['str'], '*reset': 'bool' }
|
|
|
|
}
|
2020-10-20 11:12:52 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-ssh-remove-authorized-keys:
|
|
|
|
#
|
2024-01-29 14:50:08 +03:00
|
|
|
# Remove public keys from the user .ssh/authorized_keys on Unix
|
|
|
|
# systems (not implemented for other systems). It's not an error if
|
|
|
|
# the key is already missing.
|
|
|
|
#
|
2020-10-20 11:12:52 +03:00
|
|
|
# @username: the user account to remove the authorized keys
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @keys: the public keys to remove (in OpenSSH/sshd(8) authorized_keys
|
|
|
|
# format)
|
|
|
|
#
|
2020-10-20 11:12:52 +03:00
|
|
|
# Since: 5.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-ssh-remove-authorized-keys',
|
2024-04-24 17:40:29 +03:00
|
|
|
'data': { 'username': 'str', 'keys': ['str'] }
|
|
|
|
}
|
2022-05-20 05:19:35 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestDiskStats:
|
|
|
|
#
|
|
|
|
# @read-sectors: sectors read
|
|
|
|
#
|
|
|
|
# @read-ios: reads completed successfully
|
|
|
|
#
|
|
|
|
# @read-merges: read requests merged
|
|
|
|
#
|
|
|
|
# @write-sectors: sectors written
|
|
|
|
#
|
|
|
|
# @write-ios: writes completed
|
|
|
|
#
|
|
|
|
# @write-merges: write requests merged
|
|
|
|
#
|
|
|
|
# @discard-sectors: sectors discarded
|
|
|
|
#
|
|
|
|
# @discard-ios: discards completed successfully
|
|
|
|
#
|
|
|
|
# @discard-merges: discard requests merged
|
|
|
|
#
|
|
|
|
# @flush-ios: flush requests completed successfully
|
|
|
|
#
|
|
|
|
# @read-ticks: time spent reading(ms)
|
|
|
|
#
|
|
|
|
# @write-ticks: time spent writing(ms)
|
|
|
|
#
|
|
|
|
# @discard-ticks: time spent discarding(ms)
|
|
|
|
#
|
|
|
|
# @flush-ticks: time spent flushing(ms)
|
|
|
|
#
|
|
|
|
# @ios-pgr: number of I/Os currently in flight
|
|
|
|
#
|
|
|
|
# @total-ticks: time spent doing I/Os (ms)
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @weight-ticks: weighted time spent doing I/Os since the last update
|
|
|
|
# of this field(ms)
|
2022-05-20 05:19:35 +03:00
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestDiskStats',
|
|
|
|
'data': {'*read-sectors': 'uint64',
|
|
|
|
'*read-ios': 'uint64',
|
|
|
|
'*read-merges': 'uint64',
|
|
|
|
'*write-sectors': 'uint64',
|
|
|
|
'*write-ios': 'uint64',
|
|
|
|
'*write-merges': 'uint64',
|
|
|
|
'*discard-sectors': 'uint64',
|
|
|
|
'*discard-ios': 'uint64',
|
|
|
|
'*discard-merges': 'uint64',
|
|
|
|
'*flush-ios': 'uint64',
|
|
|
|
'*read-ticks': 'uint64',
|
|
|
|
'*write-ticks': 'uint64',
|
|
|
|
'*discard-ticks': 'uint64',
|
|
|
|
'*flush-ticks': 'uint64',
|
|
|
|
'*ios-pgr': 'uint64',
|
|
|
|
'*total-ticks': 'uint64',
|
|
|
|
'*weight-ticks': 'uint64'
|
2024-07-12 16:24:48 +03:00
|
|
|
},
|
|
|
|
'if': 'CONFIG_LINUX' }
|
2022-05-20 05:19:35 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestDiskStatsInfo:
|
|
|
|
#
|
2023-04-25 09:42:18 +03:00
|
|
|
# @name: disk name
|
2022-05-20 05:19:35 +03:00
|
|
|
#
|
2023-04-25 09:42:18 +03:00
|
|
|
# @major: major device number of disk
|
2022-05-20 05:19:35 +03:00
|
|
|
#
|
2023-04-25 09:42:18 +03:00
|
|
|
# @minor: minor device number of disk
|
2024-02-05 10:47:03 +03:00
|
|
|
#
|
|
|
|
# @stats: I/O statistics
|
2022-05-20 05:19:35 +03:00
|
|
|
##
|
|
|
|
{ 'struct': 'GuestDiskStatsInfo',
|
|
|
|
'data': {'name': 'str',
|
|
|
|
'major': 'uint64',
|
|
|
|
'minor': 'uint64',
|
2024-07-12 16:24:45 +03:00
|
|
|
'stats': 'GuestDiskStats' },
|
2024-07-12 16:24:48 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2022-05-20 05:19:35 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-diskstats:
|
|
|
|
#
|
|
|
|
# Retrieve information about disk stats.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2022-05-20 05:19:35 +03:00
|
|
|
# Returns: List of disk stats of guest.
|
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-diskstats',
|
2024-07-12 16:24:45 +03:00
|
|
|
'returns': ['GuestDiskStatsInfo'],
|
2024-07-12 16:24:48 +03:00
|
|
|
'if': 'CONFIG_LINUX'
|
2022-05-20 05:19:35 +03:00
|
|
|
}
|
2022-07-07 03:56:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestCpuStatsType:
|
|
|
|
#
|
2024-02-05 10:47:03 +03:00
|
|
|
# Guest operating systems supporting CPU statistics
|
|
|
|
#
|
|
|
|
# @linux: Linux
|
2022-07-07 03:56:02 +03:00
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestCpuStatsType',
|
2024-07-12 16:24:45 +03:00
|
|
|
'data': [ 'linux' ],
|
2024-07-12 16:24:48 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2022-07-07 03:56:02 +03:00
|
|
|
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestLinuxCpuStats:
|
|
|
|
#
|
|
|
|
# CPU statistics of Linux
|
|
|
|
#
|
|
|
|
# @cpu: CPU index in guest OS
|
|
|
|
#
|
|
|
|
# @user: Time spent in user mode
|
|
|
|
#
|
|
|
|
# @nice: Time spent in user mode with low priority (nice)
|
|
|
|
#
|
|
|
|
# @system: Time spent in system mode
|
|
|
|
#
|
|
|
|
# @idle: Time spent in the idle task
|
|
|
|
#
|
|
|
|
# @iowait: Time waiting for I/O to complete (since Linux 2.5.41)
|
|
|
|
#
|
|
|
|
# @irq: Time servicing interrupts (since Linux 2.6.0-test4)
|
|
|
|
#
|
|
|
|
# @softirq: Time servicing softirqs (since Linux 2.6.0-test4)
|
|
|
|
#
|
|
|
|
# @steal: Stolen time by host (since Linux 2.6.11)
|
|
|
|
#
|
2023-04-28 13:54:28 +03:00
|
|
|
# @guest: ime spent running a virtual CPU for guest operating systems
|
|
|
|
# under the control of the Linux kernel (since Linux 2.6.24)
|
2022-07-07 03:56:02 +03:00
|
|
|
#
|
|
|
|
# @guestnice: Time spent running a niced guest (since Linux 2.6.33)
|
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestLinuxCpuStats',
|
|
|
|
'data': {'cpu': 'int',
|
|
|
|
'user': 'uint64',
|
|
|
|
'nice': 'uint64',
|
|
|
|
'system': 'uint64',
|
|
|
|
'idle': 'uint64',
|
|
|
|
'*iowait': 'uint64',
|
|
|
|
'*irq': 'uint64',
|
|
|
|
'*softirq': 'uint64',
|
|
|
|
'*steal': 'uint64',
|
|
|
|
'*guest': 'uint64',
|
|
|
|
'*guestnice': 'uint64'
|
2024-07-12 16:24:45 +03:00
|
|
|
},
|
2024-07-12 16:24:48 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2022-07-07 03:56:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestCpuStats:
|
|
|
|
#
|
|
|
|
# Get statistics of each CPU in millisecond.
|
|
|
|
#
|
2024-02-05 10:47:03 +03:00
|
|
|
# @type: guest operating system
|
2022-07-07 03:56:02 +03:00
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'union': 'GuestCpuStats',
|
|
|
|
'base': { 'type': 'GuestCpuStatsType' },
|
|
|
|
'discriminator': 'type',
|
2024-07-12 16:24:45 +03:00
|
|
|
'data': { 'linux': 'GuestLinuxCpuStats' },
|
2024-07-12 16:24:48 +03:00
|
|
|
'if': 'CONFIG_LINUX' }
|
2022-07-07 03:56:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-cpustats:
|
|
|
|
#
|
|
|
|
# Retrieve information about CPU stats.
|
2023-04-28 13:54:28 +03:00
|
|
|
#
|
2022-07-07 03:56:02 +03:00
|
|
|
# Returns: List of CPU stats of guest.
|
|
|
|
#
|
|
|
|
# Since: 7.1
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-cpustats',
|
2024-07-12 16:24:45 +03:00
|
|
|
'returns': ['GuestCpuStats'],
|
2024-07-12 16:24:48 +03:00
|
|
|
'if': 'CONFIG_LINUX'
|
2022-07-07 03:56:02 +03:00
|
|
|
}
|
2024-06-13 12:28:02 +03:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestNetworkRoute:
|
|
|
|
#
|
|
|
|
# Route information, currently, only linux supported.
|
|
|
|
#
|
|
|
|
# @iface: The destination network or host's egress network interface in the routing table
|
|
|
|
#
|
|
|
|
# @destination: The IP address of the target network or host, The final destination of the packet
|
|
|
|
#
|
|
|
|
# @metric: Route metric
|
|
|
|
#
|
|
|
|
# @gateway: The IP address of the next hop router
|
|
|
|
#
|
|
|
|
# @mask: Subnet Mask (IPv4 only)
|
|
|
|
#
|
|
|
|
# @irtt: Initial round-trip delay (not for windows, IPv4 only)
|
|
|
|
#
|
|
|
|
# @flags: Route flags (not for windows)
|
|
|
|
#
|
|
|
|
# @refcnt: The route's reference count (not for windows)
|
|
|
|
#
|
|
|
|
# @use: Route usage count (not for windows)
|
|
|
|
#
|
|
|
|
# @window: TCP window size, used for flow control (not for windows, IPv4 only)
|
|
|
|
#
|
|
|
|
# @mtu: Data link layer maximum packet size (not for windows)
|
|
|
|
#
|
|
|
|
# @desprefixlen: Destination prefix length (for IPv6)
|
|
|
|
#
|
|
|
|
# @source: Source IP address (for IPv6)
|
|
|
|
#
|
|
|
|
# @srcprefixlen: Source prefix length (for IPv6)
|
|
|
|
#
|
|
|
|
# @nexthop: Next hop IP address (for IPv6)
|
|
|
|
#
|
|
|
|
# @version: IP version (4 or 6)
|
|
|
|
#
|
|
|
|
# Since: 9.1
|
|
|
|
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestNetworkRoute',
|
|
|
|
'data': {'iface': 'str',
|
|
|
|
'destination': 'str',
|
|
|
|
'metric': 'int',
|
|
|
|
'*gateway': 'str',
|
|
|
|
'*mask': 'str',
|
|
|
|
'*irtt': 'int',
|
|
|
|
'*flags': 'uint64',
|
|
|
|
'*refcnt': 'int',
|
|
|
|
'*use': 'int',
|
|
|
|
'*window': 'int',
|
|
|
|
'*mtu': 'int',
|
|
|
|
'*desprefixlen': 'str',
|
|
|
|
'*source': 'str',
|
|
|
|
'*srcprefixlen': 'str',
|
|
|
|
'*nexthop': 'str',
|
|
|
|
'version': 'int'
|
|
|
|
},
|
|
|
|
'if': 'CONFIG_LINUX' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-network-get-route:
|
|
|
|
#
|
|
|
|
# Retrieve information about route of network.
|
|
|
|
# Returns: List of route info of guest.
|
|
|
|
#
|
|
|
|
# Since: 9.1
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-network-get-route',
|
|
|
|
'returns': ['GuestNetworkRoute'],
|
|
|
|
'if': 'CONFIG_LINUX'
|
|
|
|
}
|