QEMU 1.2.0 windows 可执行程序

QMP Supported Commands ---------------------- This document describes all commands currently supported by QMP. Most of the time their usage is exactly the same as in the user Monitor, this means that any other document which also describe commands (the manpage, QEMU's manual, etc) can and should be consulted. QMP has two types of commands: regular and query commands. Regular commands usually change the Virtual Machine's state someway, while query commands just return information. The sections below are divided accordingly. It's important to observe that all communication examples are formatted in a reader-friendly way, so that they're easier to understand. However, in real protocol usage, they're emitted as a single line. Also, the following notation is used to denote data flow: -> data issued by the Client <- Server data response Please, refer to the QMP specification (QMP/qmp-spec.txt) for detailed information on the Server command and response formats. NOTE: This document is temporary and will be replaced soon. 1. Stability Considerations =========================== The current QMP command set (described in this file) may be useful for a number of use cases, however it's limited and several commands have bad defined semantics, specially with regard to command completion. These problems are going to be solved incrementally in the next QEMU releases and we're going to establish a deprecation policy for badly defined commands. If you're planning to adopt QMP, please observe the following: 1. The deprecation policy will take effect and be documented soon, please check the documentation of each used command as soon as a new release of QEMU is available 2. DO NOT rely on anything which is not explicit documented 3. Errors, in special, are not documented. Applications should NOT check for specific errors classes or data (it's strongly recommended to only check for the "error" key) 2. Regular Commands =================== Server's responses in the examples below are always a success response, please refer to the QMP specification for more details on error responses. quit ---- Quit the emulator. Arguments: None. Example: -> { "execute": "quit" } <- { "return": {} } eject ----- Eject a removable medium. Arguments: - force: force ejection (json-bool, optional) - device: device name (json-string) Example: -> { "execute": "eject", "arguments": { "device": "ide1-cd0" } } <- { "return": {} } Note: The "force" argument defaults to false. change ------ Change a removable medium or VNC configuration. Arguments: - "device": device name (json-string) - "target": filename or item (json-string) - "arg": additional argument (json-string, optional) Examples: 1. Change a removable medium -> { "execute": "change", "arguments": { "device": "ide1-cd0", "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } } <- { "return": {} } 2. Change VNC password -> { "execute": "change", "arguments": { "device": "vnc", "target": "password", "arg": "foobar1" } } <- { "return": {} } screendump ---------- Save screen into PPM image. Arguments: - "filename": file path (json-string) Example: -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } } <- { "return": {} } stop ---- Stop the emulator. Arguments: None. Example: -> { "execute": "stop" } <- { "return": {} } cont ---- Resume emulation. Arguments: None. Example: -> { "execute": "cont" } <- { "return": {} } system_wakeup ------------- Wakeup guest from suspend. Arguments: None. Example: -> { "execute": "system_wakeup" } <- { "return": {} } system_reset ------------ Reset the system. Arguments: None. Example: -> { "execute": "system_reset" } <- { "return": {} } system_powerdown ---------------- Send system power down event. Arguments: None. Example: -> { "execute": "system_powerdown" } <- { "return": {} } device_add ---------- Add a device. Arguments: - "driver": the name of the new device's driver (json-string) - "bus": the device's parent bus (device tree path, json-string, optional) - "id": the device's ID, must be unique (json-string) - device properties Example: -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } } <- { "return": {} } Notes: (1) For detailed information about this command, please refer to the 'docs/qdev-device-use.txt' file. (2) It's possible to list device properties by running QEMU with the "-device DEVICE,\?" command-line argument, where DEVICE is the device's name device_del ---------- Remove a device. Arguments: - "id": the device's ID (json-string) Example: -> { "execute": "device_del", "arguments": { "id": "net1" } } <- { "return": {} } cpu --- Set the default CPU. Arguments: - "index": the CPU's index (json-int) Example: -> { "execute": "cpu", "arguments": { "index": 0 } } <- { "return": {} } Note: CPUs' indexes are obtained with the 'query-cpus' command. memsave ------- Save to disk virtual memory dump starting at 'val' of size 'size'. Arguments: - "val": the starting address (json-int) - "size": the memory size, in bytes (json-int) - "filename": file path (json-string) - "cpu": virtual CPU index (json-int, optional) Example: -> { "execute": "memsave", "arguments": { "val": 10, "size": 100, "filename": "/tmp/virtual-mem-dump" } } <- { "return": {} } pmemsave -------- Save to disk physical memory dump starting at 'val' of size 'size'. Arguments: - "val": the starting address (json-int) - "size": the memory size, in bytes (json-int) - "filename": file path (json-string) Example: -> { "execute": "pmemsave", "arguments": { "val": 10, "size": 100, "filename": "/tmp/physical-mem-dump" } } <- { "return": {} } inject-nmi ---------- Inject an NMI on guest's CPUs. Arguments: None. Example: -> { "execute": "inject-nmi" } <- { "return": {} } Note: inject-nmi fails when the guest doesn't support injecting. Currently, only x86 guests do. xen-save-devices-state ------- Save the state of all devices to file. The RAM and the block devices of the VM are not saved by this command. Arguments: - "filename": the file to save the state of the devices to as binary data. See xen-save-devices-state.txt for a description of the binary format. Example: -> { "execute": "xen-save-devices-state", "arguments": { "filename": "/tmp/save" } } <- { "return": {} } migrate ------- Migrate to URI. Arguments: - "blk": block migration, full disk copy (json-bool, optional) - "inc": incremental disk copy (json-bool, optional) - "uri": Destination URI (json-string) Example: -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } } <- { "return": {} } Notes: (1) The 'query-migrate' command should be used to check migration's progress and final result (this information is provided by the 'status' member) (2) All boolean arguments default to false (3) The user Monitor's "detach" argument is invalid in QMP and should not be used migrate_cancel -------------- Cancel the current migration. Arguments: None. Example: -> { "execute": "migrate_cancel" } <- { "return": {} } migrate-set-cache-size --------------------- Set cache size to be used by XBZRLE migration, the cache size will be rounded down to the nearest power of 2 Arguments: - "value": cache size in bytes (json-int) Example: -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } } <- { "return": {} } query-migrate-cache-size --------------------- Show cache size to be used by XBZRLE migration returns a json-object with the following information: - "size" : json-int Example: -> { "execute": "query-migrate-cache-size" } <- { "return": 67108864 } migrate_set_speed --