2011-07-19 22:41:55 +02:00
|
|
|
# *-*- Mode: Python -*-*
|
|
|
|
|
2013-03-15 19:07:51 +01:00
|
|
|
##
|
|
|
|
#
|
|
|
|
# General note concerning the use of guest agent interfaces:
|
|
|
|
#
|
|
|
|
# "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.
|
|
|
|
#
|
|
|
|
##
|
|
|
|
|
2012-02-07 20:56:48 +01:00
|
|
|
##
|
|
|
|
#
|
|
|
|
# Echo back a unique integer value, and prepend to response a
|
|
|
|
# leading sentinel byte (0xFF) the client can check scan for.
|
|
|
|
#
|
|
|
|
# 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).
|
|
|
|
#
|
|
|
|
# After issuing this request, all guest agent responses should be
|
|
|
|
# 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
|
2012-05-09 07:12:04 +02:00
|
|
|
# sentinel value is receiving to avoid unnecessary processing of
|
2012-02-07 20:56:48 +01:00
|
|
|
# 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.
|
|
|
|
#
|
|
|
|
# @id: randomly generated 64-bit integer
|
|
|
|
#
|
|
|
|
# Returns: The unique integer id passed in by the client
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
# ##
|
2013-01-02 17:15:11 +01:00
|
|
|
{ 'command': 'guest-sync-delimited',
|
2012-02-07 20:56:48 +01:00
|
|
|
'data': { 'id': 'int' },
|
|
|
|
'returns': 'int' }
|
|
|
|
|
2011-07-19 22:41:55 +02:00
|
|
|
##
|
|
|
|
# @guest-sync:
|
|
|
|
#
|
|
|
|
# Echo back a unique integer value
|
|
|
|
#
|
|
|
|
# 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.
|
|
|
|
#
|
2012-02-07 20:56:48 +01:00
|
|
|
# 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
|
|
|
|
# response may result in a parser error.
|
|
|
|
#
|
2011-12-10 00:19:46 +01:00
|
|
|
# Such clients should also precede this command
|
2012-02-07 20:56:48 +01:00
|
|
|
# with a 0xFF byte to make sure the guest agent flushes any
|
2011-07-19 22:41:55 +02:00
|
|
|
# partially read JSON data from a previous session.
|
|
|
|
#
|
|
|
|
# @id: randomly generated 64-bit integer
|
|
|
|
#
|
|
|
|
# Returns: The unique integer id passed in by the client
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2013-01-02 17:15:11 +01:00
|
|
|
{ 'command': 'guest-sync',
|
2011-07-19 22:41:55 +02: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 10:39:11 +01:00
|
|
|
##
|
|
|
|
# @guest-get-time:
|
|
|
|
#
|
2014-04-04 17:25:02 +02:00
|
|
|
# Get the information about guest's System Time relative to
|
|
|
|
# the Epoch of 1970-01-01 in UTC.
|
2013-03-05 10:39:11 +01:00
|
|
|
#
|
|
|
|
# Returns: Time in nanoseconds.
|
|
|
|
#
|
|
|
|
# Since 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-time',
|
|
|
|
'returns': 'int' }
|
|
|
|
|
2013-03-05 10:39:12 +01:00
|
|
|
##
|
|
|
|
# @guest-set-time:
|
|
|
|
#
|
|
|
|
# Set guest time.
|
|
|
|
#
|
|
|
|
# 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.
|
|
|
|
#
|
2014-04-04 17:25:02 +02:00
|
|
|
# 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
|
2015-01-21 12:09:50 +01:00
|
|
|
# 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
|
|
|
|
# value.
|
2013-03-05 10:39:12 +01:00
|
|
|
#
|
2014-01-31 11:29:51 +01:00
|
|
|
# @time: #optional time of nanoseconds, relative to the Epoch
|
|
|
|
# of 1970-01-01 in UTC.
|
2013-03-05 10:39:12 +01:00
|
|
|
#
|
|
|
|
# Returns: Nothing on success.
|
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-time',
|
2014-01-31 11:29:51 +01:00
|
|
|
'data': { '*time': 'int' } }
|
2013-03-05 10:39:12 +01:00
|
|
|
|
2011-07-19 22:41:55 +02:00
|
|
|
##
|
2012-01-17 00:44:16 +01:00
|
|
|
# @GuestAgentCommandInfo:
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# Information about guest agent commands.
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# @name: name of the command
|
|
|
|
#
|
|
|
|
# @enabled: whether command is currently enabled by guest admin
|
|
|
|
#
|
2013-10-09 04:37:26 +02:00
|
|
|
# @success-response: whether command returns a response on success
|
|
|
|
# (since 1.7)
|
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# Since 1.1.0
|
2011-07-19 22:41:55 +02:00
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestAgentCommandInfo',
|
2013-10-09 04:37:26 +02:00
|
|
|
'data': { 'name': 'str', 'enabled': 'bool', 'success-response': 'bool' } }
|
2012-01-17 00:44:16 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestAgentInfo
|
|
|
|
#
|
|
|
|
# Information about guest agent.
|
|
|
|
#
|
|
|
|
# @version: guest agent version
|
|
|
|
#
|
|
|
|
# @supported_commands: Information about guest agent commands
|
|
|
|
#
|
|
|
|
# Since 0.15.0
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestAgentInfo',
|
2011-12-07 05:03:43 +01:00
|
|
|
'data': { 'version': 'str',
|
|
|
|
'supported_commands': ['GuestAgentCommandInfo'] } }
|
2012-01-17 00:44:16 +01:00
|
|
|
##
|
|
|
|
# @guest-info:
|
|
|
|
#
|
|
|
|
# Get some information about the guest agent.
|
|
|
|
#
|
|
|
|
# Returns: @GuestAgentInfo
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2011-07-19 22:41:55 +02:00
|
|
|
{ 'command': 'guest-info',
|
|
|
|
'returns': 'GuestAgentInfo' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-shutdown:
|
|
|
|
#
|
|
|
|
# Initiate guest-activated shutdown. Note: this is an asynchronous
|
2012-05-14 20:25:20 +02:00
|
|
|
# shutdown request, with no guarantee of successful shutdown.
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# @mode: #optional "halt", "powerdown" (default), or "reboot"
|
|
|
|
#
|
2012-05-08 19:24:46 +02: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-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2012-05-08 19:24:46 +02: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 17:05:19 +02:00
|
|
|
'success-response': false }
|
2011-07-19 22:41:55 +02:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-file-open:
|
|
|
|
#
|
|
|
|
# Open a file in the guest and retrieve a file handle for it
|
|
|
|
#
|
|
|
|
# @filepath: Full path to the file in the guest to open.
|
|
|
|
#
|
|
|
|
# @mode: #optional open mode, as per fopen(), "r" is the default.
|
|
|
|
#
|
|
|
|
# Returns: Guest file handle on success.
|
|
|
|
#
|
|
|
|
# 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
|
|
|
|
#
|
|
|
|
# Returns: Nothing on success.
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-close',
|
|
|
|
'data': { 'handle': 'int' } }
|
|
|
|
|
2012-01-17 00:44:16 +01:00
|
|
|
##
|
|
|
|
# @GuestFileRead
|
|
|
|
#
|
|
|
|
# Result of guest agent file-read operation
|
|
|
|
#
|
|
|
|
# @count: number of bytes read (note: count is *before*
|
|
|
|
# base64-encoding is applied)
|
|
|
|
#
|
|
|
|
# @buf-b64: base64-encoded bytes read
|
|
|
|
#
|
|
|
|
# @eof: whether EOF was encountered during read operation.
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestFileRead',
|
2012-01-17 00:44:16 +01:00
|
|
|
'data': { 'count': 'int', 'buf-b64': 'str', 'eof': 'bool' } }
|
|
|
|
|
2011-07-19 22:41:55 +02:00
|
|
|
##
|
|
|
|
# @guest-file-read:
|
|
|
|
#
|
|
|
|
# Read from an open file in the guest. Data will be base64-encoded
|
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# @count: #optional maximum number of bytes to read (default is 4KB)
|
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# Returns: @GuestFileRead on success.
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-read',
|
|
|
|
'data': { 'handle': 'int', '*count': 'int' },
|
|
|
|
'returns': 'GuestFileRead' }
|
|
|
|
|
2012-01-17 00:44:16 +01:00
|
|
|
##
|
|
|
|
# @GuestFileWrite
|
|
|
|
#
|
|
|
|
# Result of guest agent file-write operation
|
|
|
|
#
|
|
|
|
# @count: number of bytes written (note: count is actual bytes
|
|
|
|
# written, after base64-decoding of provided buffer)
|
|
|
|
#
|
|
|
|
# @eof: whether EOF was encountered during write operation.
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestFileWrite',
|
2012-01-17 00:44:16 +01:00
|
|
|
'data': { 'count': 'int', 'eof': 'bool' } }
|
|
|
|
|
2011-07-19 22:41:55 +02: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
|
|
|
|
#
|
|
|
|
# @count: #optional bytes to write (actual bytes, after base64-decode),
|
|
|
|
# default is all content in buf-b64 buffer after base64 decoding
|
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# Returns: @GuestFileWrite on success.
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-write',
|
|
|
|
'data': { 'handle': 'int', 'buf-b64': 'str', '*count': 'int' },
|
|
|
|
'returns': 'GuestFileWrite' }
|
|
|
|
|
2012-01-17 00:44:16 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestFileSeek
|
|
|
|
#
|
|
|
|
# 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 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestFileSeek',
|
2012-01-17 00:44:16 +01:00
|
|
|
'data': { 'position': 'int', 'eof': 'bool' } }
|
|
|
|
|
2011-07-19 22:41:55 +02:00
|
|
|
##
|
|
|
|
# @guest-file-seek:
|
|
|
|
#
|
|
|
|
# Seek to a position in the file, as with fseek(), and return the
|
|
|
|
# current file position afterward. Also encapsulates ftell()'s
|
|
|
|
# functionality, just Set offset=0, whence=SEEK_CUR.
|
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# @offset: bytes to skip over in the file stream
|
|
|
|
#
|
|
|
|
# @whence: SEEK_SET, SEEK_CUR, or SEEK_END, as with fseek()
|
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# Returns: @GuestFileSeek on success.
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-seek',
|
|
|
|
'data': { 'handle': 'int', 'offset': 'int', 'whence': 'int' },
|
|
|
|
'returns': 'GuestFileSeek' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-file-flush:
|
|
|
|
#
|
|
|
|
# Write file changes bufferred in userspace to disk/kernel buffers
|
|
|
|
#
|
|
|
|
# @handle: filehandle returned by guest-file-open
|
|
|
|
#
|
|
|
|
# Returns: Nothing on success.
|
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-file-flush',
|
|
|
|
'data': { 'handle': 'int' } }
|
|
|
|
|
|
|
|
##
|
2012-01-17 00:44:16 +01:00
|
|
|
# @GuestFsFreezeStatus
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
2012-08-23 07:14:25 +02:00
|
|
|
# An enumeration of filesystem freeze states
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# @thawed: filesystems thawed/unfrozen
|
|
|
|
#
|
|
|
|
# @frozen: all non-network guest filesystems frozen
|
|
|
|
#
|
2011-07-19 22:41:55 +02:00
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestFsfreezeStatus',
|
2012-04-17 02:52:17 +02:00
|
|
|
'data': [ 'thawed', 'frozen' ] }
|
2012-01-17 00:44:16 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-fsfreeze-status:
|
|
|
|
#
|
|
|
|
# Get guest fsfreeze state. error state indicates
|
|
|
|
#
|
|
|
|
# Returns: GuestFsfreezeStatus ("thawed", "frozen", etc., as defined below)
|
|
|
|
#
|
2012-04-17 02:52:17 +02:00
|
|
|
# Note: This may fail to properly report the current state as a result of
|
qemu-ga: persist tracking of fsfreeze state via filesystem
Currently, qemu-ga may die/get killed/go away for whatever reason after
guest-fsfreeze-freeze has been issued, and before guest-fsfreeze-thaw
has been issued. This means the only way to unfreeze the guest is via
VNC/network/console access, but obtaining that access after-the-fact can
often be very difficult when filesystems are frozen. Logins will almost
always hang, for instance. In many cases the only recourse would be to
reboot the guest without any quiescing of volatile state, which makes
this a corner-case worth giving some attention to.
A likely failsafe for this situation would be to use a watchdog to
restart qemu-ga if it goes away. There are some precautions qemu-ga
needs to take in order to avoid immediately hanging itself on I/O,
however, namely, we must disable logging and defer to processing/creation
of user-specific logfiles, along with creation of the pid file if we're
running as a daemon. We also need to disable non-fsfreeze-safe commands,
as we normally would when processing the guest-fsfreeze-freeze command.
To track when we need to do this in a way that persists between multiple
invocations of qemu-ga, we create a file on the guest filesystem before
issuing the fsfreeze, and delete it when doing the thaw. On qemu-ga
startup, we check for the existance of this file to determine
the need to take the above precautions.
We're forced to do it this way since a more traditional approach such as
reading/writing state to a dedicated state file will cause
access/modification time updates, respectively, both of which will hang
if the file resides on a frozen filesystem. Both can occur even if
relatime is enabled. Checking for file existence will not update the
access time, however, so it's a safe way to check for fsfreeze state.
An actual watchdog-based restart of qemu-ga can itself cause an access
time update that would thus hang the invocation of qemu-ga, but the
logic to workaround that can be handled via the watchdog, so we don't
address that here (for relatime we'd periodically touch the qemu-ga
binary if the file $qga_statedir/qga.state.isfrozen is not present, this
avoids qemu-ga updates or the 1 day relatime threshold causing an
access-time update if we try to respawn qemu-ga shortly after it goes
away)
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
2012-04-18 23:28:01 +02:00
|
|
|
# some other guest processes having issued an fs freeze/thaw.
|
2012-04-17 02:52:17 +02:00
|
|
|
#
|
2012-01-17 00:44:16 +01:00
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
2011-07-19 22:41:55 +02:00
|
|
|
{ 'command': 'guest-fsfreeze-status',
|
|
|
|
'returns': 'GuestFsfreezeStatus' }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-fsfreeze-freeze:
|
|
|
|
#
|
2012-04-17 02:52:17 +02:00
|
|
|
# Sync and freeze all freezable, local guest filesystems
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
2012-04-17 02:52:17 +02:00
|
|
|
# Returns: Number of file systems currently frozen. On error, all filesystems
|
|
|
|
# will be thawed.
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fsfreeze-freeze',
|
|
|
|
'returns': 'int' }
|
|
|
|
|
2014-06-30 23:51:27 +02:00
|
|
|
##
|
|
|
|
# @guest-fsfreeze-freeze-list:
|
|
|
|
#
|
|
|
|
# Sync and freeze specified guest filesystems
|
|
|
|
#
|
|
|
|
# @mountpoints: #optional an array of mountpoints of filesystems to be frozen.
|
|
|
|
# If omitted, every mounted filesystem is frozen.
|
|
|
|
#
|
|
|
|
# Returns: Number of file systems currently frozen. On error, all filesystems
|
|
|
|
# will be thawed.
|
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fsfreeze-freeze-list',
|
|
|
|
'data': { '*mountpoints': ['str'] },
|
|
|
|
'returns': 'int' }
|
|
|
|
|
2011-07-19 22:41:55 +02:00
|
|
|
##
|
|
|
|
# @guest-fsfreeze-thaw:
|
|
|
|
#
|
2012-04-17 02:52:17 +02:00
|
|
|
# Unfreeze all frozen guest filesystems
|
|
|
|
#
|
|
|
|
# Returns: Number of file systems thawed by this call
|
2011-07-19 22:41:55 +02:00
|
|
|
#
|
2012-04-17 02:52:17 +02:00
|
|
|
# Note: if return value does not match the previous call to
|
|
|
|
# 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-19 22:41:55 +02:00
|
|
|
#
|
|
|
|
# Since: 0.15.0
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fsfreeze-thaw',
|
|
|
|
'returns': 'int' }
|
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 15:03:03 +01:00
|
|
|
|
2015-05-11 08:58:45 +02:00
|
|
|
##
|
|
|
|
# @GuestFilesystemTrimResult
|
|
|
|
#
|
|
|
|
# @path: path that was trimmed
|
|
|
|
# @error: an error message when trim failed
|
|
|
|
# @trimmed: bytes trimmed for this path
|
|
|
|
# @minimum: reported effective minimum for this path
|
|
|
|
#
|
|
|
|
# Since: 2.4
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestFilesystemTrimResult',
|
|
|
|
'data': {'path': 'str',
|
|
|
|
'*trimmed': 'int', '*minimum': 'int', '*error': 'str'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestFilesystemTrimResponse
|
|
|
|
#
|
|
|
|
# @paths: list of @GuestFilesystemTrimResult per path that was trimmed
|
|
|
|
#
|
|
|
|
# Since: 2.4
|
|
|
|
##
|
|
|
|
{ 'struct': 'GuestFilesystemTrimResponse',
|
|
|
|
'data': {'paths': ['GuestFilesystemTrimResult']} }
|
|
|
|
|
2012-06-13 07:41:28 +02:00
|
|
|
##
|
|
|
|
# @guest-fstrim:
|
|
|
|
#
|
|
|
|
# Discard (or "trim") blocks which are not in use by the filesystem.
|
|
|
|
#
|
|
|
|
# @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".
|
|
|
|
#
|
2015-05-11 08:58:45 +02:00
|
|
|
# Returns: A @GuestFilesystemTrimResponse which contains the
|
|
|
|
# status of all trimmed paths. (since 2.4)
|
2012-06-13 07:41:28 +02:00
|
|
|
#
|
|
|
|
# Since: 1.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-fstrim',
|
2015-05-11 08:58:45 +02:00
|
|
|
'data': { '*minimum': 'int' },
|
|
|
|
'returns': 'GuestFilesystemTrimResponse' }
|
2012-06-13 07:41:28 +02: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 15:03:03 +01:00
|
|
|
##
|
|
|
|
# @guest-suspend-disk
|
|
|
|
#
|
|
|
|
# Suspend guest to disk.
|
|
|
|
#
|
|
|
|
# This command tries to execute the scripts provided by the pm-utils package.
|
|
|
|
# If it's not available, the suspend operation will be performed by manually
|
|
|
|
# writing to a sysfs file.
|
|
|
|
#
|
|
|
|
# For the best results it's strongly recommended to have the pm-utils
|
|
|
|
# package installed in the guest.
|
|
|
|
#
|
2012-05-08 19:24:47 +02: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.
|
|
|
|
#
|
|
|
|
# The following errors may be returned:
|
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 15:03:03 +01:00
|
|
|
# If suspend to disk is not supported, Unsupported
|
|
|
|
#
|
2012-05-08 19:24:47 +02:00
|
|
|
# Notes: 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 15:03:03 +01:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
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 17:05:19 +02:00
|
|
|
{ 'command': 'guest-suspend-disk', 'success-response': false }
|
2012-02-28 15:03:04 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-suspend-ram
|
|
|
|
#
|
|
|
|
# Suspend guest to ram.
|
|
|
|
#
|
|
|
|
# This command tries to execute the scripts provided by the pm-utils package.
|
|
|
|
# If it's not available, the suspend operation will be performed by manually
|
|
|
|
# writing to a sysfs file.
|
|
|
|
#
|
|
|
|
# For the best results it's strongly recommended to have the pm-utils
|
|
|
|
# package installed in the guest.
|
|
|
|
#
|
|
|
|
# IMPORTANT: guest-suspend-ram requires QEMU to support the 'system_wakeup'
|
|
|
|
# command. Thus, it's *required* to query QEMU for the presence of the
|
|
|
|
# 'system_wakeup' command before issuing guest-suspend-ram.
|
|
|
|
#
|
2012-05-08 19:24:48 +02:00
|
|
|
# This command does NOT return a response on success. There are two options
|
|
|
|
# to check for success:
|
|
|
|
# 1. Wait for the SUSPEND QMP event from QEMU
|
|
|
|
# 2. Issue the query-status QMP command to confirm the VM status is
|
|
|
|
# "suspended"
|
|
|
|
#
|
|
|
|
# The following errors may be returned:
|
2012-02-28 15:03:04 +01:00
|
|
|
# If suspend to ram is not supported, Unsupported
|
|
|
|
#
|
2012-05-08 19:24:48 +02:00
|
|
|
# Notes: It's strongly recommended to issue the guest-sync command before
|
|
|
|
# sending commands when the guest resumes
|
2012-02-28 15:03:04 +01:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
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 17:05:19 +02:00
|
|
|
{ 'command': 'guest-suspend-ram', 'success-response': false }
|
2012-02-28 15:03:05 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-suspend-hybrid
|
|
|
|
#
|
|
|
|
# Save guest state to disk and suspend to ram.
|
|
|
|
#
|
|
|
|
# This command requires the pm-utils package to be installed in the guest.
|
|
|
|
#
|
|
|
|
# IMPORTANT: guest-suspend-hybrid requires QEMU to support the 'system_wakeup'
|
|
|
|
# command. Thus, it's *required* to query QEMU for the presence of the
|
|
|
|
# 'system_wakeup' command before issuing guest-suspend-hybrid.
|
|
|
|
#
|
2012-05-08 19:24:49 +02:00
|
|
|
# This command does NOT return a response on success. There are two options
|
|
|
|
# to check for success:
|
|
|
|
# 1. Wait for the SUSPEND QMP event from QEMU
|
|
|
|
# 2. Issue the query-status QMP command to confirm the VM status is
|
|
|
|
# "suspended"
|
|
|
|
#
|
|
|
|
# The following errors may be returned:
|
2012-02-28 15:03:05 +01:00
|
|
|
# If hybrid suspend is not supported, Unsupported
|
|
|
|
#
|
2012-05-08 19:24:49 +02:00
|
|
|
# Notes: It's strongly recommended to issue the guest-sync command before
|
|
|
|
# sending commands when the guest resumes
|
2012-02-28 15:03:05 +01:00
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
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 17:05:19 +02:00
|
|
|
{ 'command': 'guest-suspend-hybrid', 'success-response': false }
|
2012-02-29 17:02:23 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestIpAddressType:
|
|
|
|
#
|
|
|
|
# An enumeration of supported IP address types
|
|
|
|
#
|
|
|
|
# @ipv4: IP version 4
|
|
|
|
#
|
|
|
|
# @ipv6: IP version 6
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestIpAddressType',
|
|
|
|
'data': [ 'ipv4', 'ipv6' ] }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @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 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestIpAddress',
|
2012-02-29 17:02:23 +01:00
|
|
|
'data': {'ip-address': 'str',
|
|
|
|
'ip-address-type': 'GuestIpAddressType',
|
|
|
|
'prefix': 'int'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @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
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestNetworkInterface',
|
2012-02-29 17:02:23 +01:00
|
|
|
'data': {'name': 'str',
|
|
|
|
'*hardware-address': 'str',
|
|
|
|
'*ip-addresses': ['GuestIpAddress'] } }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-network-get-interfaces:
|
|
|
|
#
|
|
|
|
# Get list of guest IP addresses, MAC addresses
|
|
|
|
# and netmasks.
|
|
|
|
#
|
|
|
|
# Returns: List of GuestNetworkInfo on success.
|
|
|
|
#
|
|
|
|
# Since: 1.1
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-network-get-interfaces',
|
|
|
|
'returns': ['GuestNetworkInterface'] }
|
2013-03-06 22:59:29 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestLogicalProcessor:
|
|
|
|
#
|
|
|
|
# @logical-id: Arbitrary guest-specific unique identifier of the VCPU.
|
|
|
|
#
|
|
|
|
# @online: Whether the VCPU is enabled.
|
|
|
|
#
|
2013-03-15 19:07:50 +01:00
|
|
|
# @can-offline: #optional 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-06 22:59:29 +01:00
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestLogicalProcessor',
|
2013-03-06 22:59:29 +01:00
|
|
|
'data': {'logical-id': 'int',
|
|
|
|
'online': 'bool',
|
|
|
|
'*can-offline': 'bool'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-vcpus:
|
|
|
|
#
|
|
|
|
# Retrieve the list of the guest's logical processors.
|
|
|
|
#
|
|
|
|
# This is a read-only operation.
|
|
|
|
#
|
|
|
|
# Returns: The list of all VCPUs the guest knows about. Each VCPU is put on the
|
|
|
|
# list exactly once, but their order is unspecified.
|
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-vcpus',
|
|
|
|
'returns': ['GuestLogicalProcessor'] }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-set-vcpus:
|
|
|
|
#
|
|
|
|
# Attempt to reconfigure (currently: enable/disable) logical processors inside
|
|
|
|
# the guest.
|
|
|
|
#
|
|
|
|
# The input 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.
|
|
|
|
#
|
|
|
|
# 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,
|
|
|
|
#
|
|
|
|
# Error: processing the first node of @vcpus failed for the
|
|
|
|
# reason returned. 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.
|
|
|
|
#
|
|
|
|
# Since: 1.5
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-vcpus',
|
|
|
|
'data': {'vcpus': ['GuestLogicalProcessor'] },
|
|
|
|
'returns': 'int' }
|
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-06-30 23:51:34 +02:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestDiskBusType
|
|
|
|
#
|
|
|
|
# An enumeration of bus type of disks
|
|
|
|
#
|
|
|
|
# @ide: IDE disks
|
|
|
|
# @fdc: floppy disks
|
|
|
|
# @scsi: SCSI disks
|
|
|
|
# @virtio: virtio disks
|
|
|
|
# @xen: Xen disks
|
|
|
|
# @usb: USB disks
|
|
|
|
# @uml: UML disks
|
|
|
|
# @sata: SATA disks
|
|
|
|
# @sd: SD cards
|
2015-06-30 12:25:22 +02:00
|
|
|
# @unknown: Unknown bus type
|
|
|
|
# @ieee1394: Win IEEE 1394 bus type
|
|
|
|
# @ssa: Win SSA bus type
|
|
|
|
# @fibre: Win fiber channel bus type
|
|
|
|
# @raid: Win RAID bus type
|
|
|
|
# @iscsi: Win iScsi bus type
|
|
|
|
# @sas: Win serial-attaches SCSI bus type
|
|
|
|
# @mmc: Win multimedia card (MMC) bus type
|
|
|
|
# @virtual: Win virtual bus type
|
|
|
|
# @file-backed virtual: Win file-backed bus type
|
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-06-30 23:51:34 +02:00
|
|
|
#
|
2015-07-21 14:25:08 +02: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-06-30 23:51:34 +02:00
|
|
|
##
|
|
|
|
{ 'enum': 'GuestDiskBusType',
|
|
|
|
'data': [ 'ide', 'fdc', 'scsi', 'virtio', 'xen', 'usb', 'uml', 'sata',
|
2015-06-30 12:25:22 +02:00
|
|
|
'sd', 'unknown', 'ieee1394', 'ssa', 'fibre', 'raid', 'iscsi',
|
|
|
|
'sas', 'mmc', 'virtual', 'file-backed-virtual' ] }
|
|
|
|
|
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-06-30 23:51:34 +02:00
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestPCIAddress:
|
|
|
|
#
|
|
|
|
# @domain: domain id
|
|
|
|
# @bus: bus id
|
|
|
|
# @slot: slot id
|
|
|
|
# @function: function id
|
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
2015-05-04 17:05:27 +02: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-06-30 23:51:34 +02:00
|
|
|
'data': {'domain': 'int', 'bus': 'int',
|
|
|
|
'slot': 'int', 'function': 'int'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestDiskAddress:
|
|
|
|
#
|
|
|
|
# @pci-controller: controller's PCI address
|
|
|
|
# @type: bus type
|
|
|
|
# @bus: bus id
|
|
|
|
# @target: target id
|
|
|
|
# @unit: unit id
|
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
2015-05-04 17:05:27 +02: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-06-30 23:51:34 +02:00
|
|
|
'data': {'pci-controller': 'GuestPCIAddress',
|
|
|
|
'bus-type': 'GuestDiskBusType',
|
|
|
|
'bus': 'int', 'target': 'int', 'unit': 'int'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestFilesystemInfo
|
|
|
|
#
|
|
|
|
# @name: disk name
|
|
|
|
# @mountpoint: mount point path
|
|
|
|
# @type: file system type string
|
|
|
|
# @disk: an array of disk hardware information that the volume lies on,
|
|
|
|
# which may be empty if the disk type is not supported
|
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
2015-05-04 17:05:27 +02: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-06-30 23:51:34 +02:00
|
|
|
'data': {'name': 'str', 'mountpoint': 'str', 'type': 'str',
|
|
|
|
'disk': ['GuestDiskAddress']} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-fsinfo:
|
|
|
|
#
|
|
|
|
# Returns: The list of filesystems information mounted in the guest.
|
|
|
|
# The returned mountpoints may be specified to
|
|
|
|
# @guest-fsfreeze-freeze-list.
|
|
|
|
# Network filesystems (such as CIFS and NFS) are not listed.
|
|
|
|
#
|
|
|
|
# Since: 2.2
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-fsinfo',
|
|
|
|
'returns': ['GuestFilesystemInfo'] }
|
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 12:26:12 +01:00
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-set-user-password
|
|
|
|
#
|
|
|
|
# @username: the user account whose password to change
|
|
|
|
# @password: the new password entry string, base64 encoded
|
|
|
|
# @crypted: true if password is already crypt()d, false if raw
|
|
|
|
#
|
|
|
|
# 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.
|
|
|
|
#
|
|
|
|
# Note all guest operating systems will support use of the
|
|
|
|
# @crypted flag, as they may require the clear-text password
|
|
|
|
#
|
|
|
|
# The @password parameter must always be base64 encoded before
|
|
|
|
# transmission, even if already crypt()d, to ensure it is 8-bit
|
|
|
|
# safe when passed as JSON.
|
|
|
|
#
|
|
|
|
# Returns: Nothing on success.
|
|
|
|
#
|
|
|
|
# Since 2.3
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-user-password',
|
|
|
|
'data': { 'username': 'str', 'password': 'str', 'crypted': 'bool' } }
|
2015-01-22 03:40:02 +01:00
|
|
|
|
|
|
|
# @GuestMemoryBlock:
|
|
|
|
#
|
|
|
|
# @phys-index: Arbitrary guest-specific unique identifier of the MEMORY BLOCK.
|
|
|
|
#
|
|
|
|
# @online: Whether the MEMORY BLOCK is enabled in guest.
|
|
|
|
#
|
|
|
|
# @can-offline: #optional 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).
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestMemoryBlock',
|
2015-01-22 03:40:02 +01:00
|
|
|
'data': {'phys-index': 'uint64',
|
|
|
|
'online': 'bool',
|
|
|
|
'*can-offline': 'bool'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-memory-blocks:
|
|
|
|
#
|
|
|
|
# Retrieve the list of the guest's memory blocks.
|
|
|
|
#
|
|
|
|
# This is a read-only operation.
|
|
|
|
#
|
|
|
|
# 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.
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-memory-blocks',
|
|
|
|
'returns': ['GuestMemoryBlock'] }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestMemoryBlockResponseType
|
|
|
|
#
|
|
|
|
# An enumeration of memory block operation result.
|
|
|
|
#
|
2015-04-09 20:32:39 +02:00
|
|
|
# @success: the operation of online/offline memory block is successful.
|
2015-01-22 03:40:02 +01:00
|
|
|
# @not-found: can't find the corresponding memoryXXX directory in sysfs.
|
|
|
|
# @operation-not-supported: for some old kernels, it does not support
|
|
|
|
# online or offline memory block.
|
|
|
|
# @operation-failed: the operation of online/offline memory block fails,
|
|
|
|
# because of some errors happen.
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'enum': 'GuestMemoryBlockResponseType',
|
|
|
|
'data': ['success', 'not-found', 'operation-not-supported',
|
|
|
|
'operation-failed'] }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @GuestMemoryBlockResponse:
|
|
|
|
#
|
|
|
|
# @phys-index: same with the 'phys-index' member of @GuestMemoryBlock.
|
|
|
|
#
|
|
|
|
# @response: the result of memory block operation.
|
|
|
|
#
|
|
|
|
# @error-code: #optional 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.
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestMemoryBlockResponse',
|
2015-01-22 03:40:02 +01:00
|
|
|
'data': { 'phys-index': 'uint64',
|
|
|
|
'response': 'GuestMemoryBlockResponseType',
|
|
|
|
'*error-code': 'int' }}
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-set-memory-blocks:
|
|
|
|
#
|
|
|
|
# Attempt to reconfigure (currently: enable/disable) state of memory blocks
|
|
|
|
# inside the guest.
|
|
|
|
#
|
|
|
|
# The input 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.
|
|
|
|
#
|
|
|
|
# Returns: The operation results, it is a list of @GuestMemoryBlockResponse,
|
|
|
|
# which is corresponding to the input list.
|
|
|
|
#
|
|
|
|
# Note: it will return NULL if the @mem-blks list was empty on input,
|
|
|
|
# or there is an error, and in this case, guest state will not be
|
|
|
|
# changed.
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-set-memory-blocks',
|
|
|
|
'data': {'mem-blks': ['GuestMemoryBlock'] },
|
|
|
|
'returns': ['GuestMemoryBlockResponse'] }
|
|
|
|
|
|
|
|
# @GuestMemoryBlockInfo:
|
|
|
|
#
|
|
|
|
# @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).
|
|
|
|
#
|
|
|
|
# Since: 2.3
|
|
|
|
##
|
2015-05-04 17:05:27 +02:00
|
|
|
{ 'struct': 'GuestMemoryBlockInfo',
|
2015-01-22 03:40:02 +01:00
|
|
|
'data': {'size': 'uint64'} }
|
|
|
|
|
|
|
|
##
|
|
|
|
# @guest-get-memory-block-info:
|
|
|
|
#
|
|
|
|
# Get information relating to guest memory blocks.
|
|
|
|
#
|
|
|
|
# Returns: memory block size in bytes.
|
|
|
|
# Returns: @GuestMemoryBlockInfo
|
|
|
|
#
|
|
|
|
# Since 2.3
|
|
|
|
##
|
|
|
|
{ 'command': 'guest-get-memory-block-info',
|
|
|
|
'returns': 'GuestMemoryBlockInfo' }
|