+1

MAINTAINERS

··· 1338 1338 F: util/main-loop.c 1339 1339 F: util/qemu-timer.c 1340 1340 F: vl.c 1341 1341 + F: qapi/run-state.json 1341 1342 1342 1343 Human Monitor (HMP) 1343 1344 M: Dr. David Alan Gilbert <dgilbert@redhat.com>

+1

Makefile

··· 413 413 $(SRC_PATH)/qapi/crypto.json \ 414 414 $(SRC_PATH)/qapi/event.json $(SRC_PATH)/qapi/introspect.json \ 415 415 $(SRC_PATH)/qapi/rocker.json \ 416 416 + $(SRC_PATH)/qapi/run-state.json \ 416 417 $(SRC_PATH)/qapi/sockets.json \ 417 418 $(SRC_PATH)/qapi/trace.json 418 419

+1 -164

qapi-schema.json

··· 80 80 81 81 { 'include': 'qapi/common.json' } 82 82 { 'include': 'qapi/sockets.json' } 83 83 + { 'include': 'qapi/run-state.json' } 83 84 { 'include': 'qapi/crypto.json' } 84 85 { 'include': 'qapi/block.json' } 85 86 { 'include': 'qapi/rocker.json' } ··· 241 242 # 242 243 ## 243 244 { 'command': 'query-kvm', 'returns': 'KvmInfo' } 244 244 - 245 245 - ## 246 246 - # @RunState: 247 247 - # 248 248 - # An enumeration of VM run states. 249 249 - # 250 250 - # @debug: QEMU is running on a debugger 251 251 - # 252 252 - # @finish-migrate: guest is paused to finish the migration process 253 253 - # 254 254 - # @inmigrate: guest is paused waiting for an incoming migration. Note 255 255 - # that this state does not tell whether the machine will start at the 256 256 - # end of the migration. This depends on the command-line -S option and 257 257 - # any invocation of 'stop' or 'cont' that has happened since QEMU was 258 258 - # started. 259 259 - # 260 260 - # @internal-error: An internal error that prevents further guest execution 261 261 - # has occurred 262 262 - # 263 263 - # @io-error: the last IOP has failed and the device is configured to pause 264 264 - # on I/O errors 265 265 - # 266 266 - # @paused: guest has been paused via the 'stop' command 267 267 - # 268 268 - # @postmigrate: guest is paused following a successful 'migrate' 269 269 - # 270 270 - # @prelaunch: QEMU was started with -S and guest has not started 271 271 - # 272 272 - # @restore-vm: guest is paused to restore VM state 273 273 - # 274 274 - # @running: guest is actively running 275 275 - # 276 276 - # @save-vm: guest is paused to save the VM state 277 277 - # 278 278 - # @shutdown: guest is shut down (and -no-shutdown is in use) 279 279 - # 280 280 - # @suspended: guest is suspended (ACPI S3) 281 281 - # 282 282 - # @watchdog: the watchdog action is configured to pause and has been triggered 283 283 - # 284 284 - # @guest-panicked: guest has been panicked as a result of guest OS panic 285 285 - # 286 286 - # @colo: guest is paused to save/restore VM state under colo checkpoint, 287 287 - # VM can not get into this state unless colo capability is enabled 288 288 - # for migration. (since 2.8) 289 289 - ## 290 290 - { 'enum': 'RunState', 291 291 - 'data': [ 'debug', 'inmigrate', 'internal-error', 'io-error', 'paused', 292 292 - 'postmigrate', 'prelaunch', 'finish-migrate', 'restore-vm', 293 293 - 'running', 'save-vm', 'shutdown', 'suspended', 'watchdog', 294 294 - 'guest-panicked', 'colo' ] } 295 295 - 296 296 - ## 297 297 - # @StatusInfo: 298 298 - # 299 299 - # Information about VCPU run state 300 300 - # 301 301 - # @running: true if all VCPUs are runnable, false if not runnable 302 302 - # 303 303 - # @singlestep: true if VCPUs are in single-step mode 304 304 - # 305 305 - # @status: the virtual machine @RunState 306 306 - # 307 307 - # Since: 0.14.0 308 308 - # 309 309 - # Notes: @singlestep is enabled through the GDB stub 310 310 - ## 311 311 - { 'struct': 'StatusInfo', 312 312 - 'data': {'running': 'bool', 'singlestep': 'bool', 'status': 'RunState'} } 313 313 - 314 314 - ## 315 315 - # @query-status: 316 316 - # 317 317 - # Query the run status of all VCPUs 318 318 - # 319 319 - # Returns: @StatusInfo reflecting all VCPUs 320 320 - # 321 321 - # Since: 0.14.0 322 322 - # 323 323 - # Example: 324 324 - # 325 325 - # -> { "execute": "query-status" } 326 326 - # <- { "return": { "running": true, 327 327 - # "singlestep": false, 328 328 - # "status": "running" } } 329 329 - # 330 330 - ## 331 331 - { 'command': 'query-status', 'returns': 'StatusInfo' } 332 245 333 246 ## 334 247 # @UuidInfo: ··· 6017 5930 { 'command': 'query-acpi-ospm-status', 'returns': ['ACPIOSTInfo'] } 6018 5931 6019 5932 ## 6020 6020 - # @WatchdogExpirationAction: 6021 6021 - # 6022 6022 - # An enumeration of the actions taken when the watchdog device's timer is 6023 6023 - # expired 6024 6024 - # 6025 6025 - # @reset: system resets 6026 6026 - # 6027 6027 - # @shutdown: system shutdown, note that it is similar to @powerdown, which 6028 6028 - # tries to set to system status and notify guest 6029 6029 - # 6030 6030 - # @poweroff: system poweroff, the emulator program exits 6031 6031 - # 6032 6032 - # @pause: system pauses, similar to @stop 6033 6033 - # 6034 6034 - # @debug: system enters debug state 6035 6035 - # 6036 6036 - # @none: nothing is done 6037 6037 - # 6038 6038 - # @inject-nmi: a non-maskable interrupt is injected into the first VCPU (all 6039 6039 - # VCPUS on x86) (since 2.4) 6040 6040 - # 6041 6041 - # Since: 2.1 6042 6042 - ## 6043 6043 - { 'enum': 'WatchdogExpirationAction', 6044 6044 - 'data': [ 'reset', 'shutdown', 'poweroff', 'pause', 'debug', 'none', 6045 6045 - 'inject-nmi' ] } 6046 6046 - 6047 6047 - ## 6048 5933 # @IoOperationType: 6049 5934 # 6050 5935 # An enumeration of the I/O operation types ··· 6057 5942 ## 6058 5943 { 'enum': 'IoOperationType', 6059 5944 'data': [ 'read', 'write' ] } 6060 6060 - 6061 6061 - ## 6062 6062 - # @GuestPanicAction: 6063 6063 - # 6064 6064 - # An enumeration of the actions taken when guest OS panic is detected 6065 6065 - # 6066 6066 - # @pause: system pauses 6067 6067 - # 6068 6068 - # Since: 2.1 (poweroff since 2.8) 6069 6069 - ## 6070 6070 - { 'enum': 'GuestPanicAction', 6071 6071 - 'data': [ 'pause', 'poweroff' ] } 6072 6072 - 6073 6073 - ## 6074 6074 - # @GuestPanicInformationType: 6075 6075 - # 6076 6076 - # An enumeration of the guest panic information types 6077 6077 - # 6078 6078 - # Since: 2.9 6079 6079 - ## 6080 6080 - { 'enum': 'GuestPanicInformationType', 6081 6081 - 'data': [ 'hyper-v'] } 6082 6082 - 6083 6083 - ## 6084 6084 - # @GuestPanicInformation: 6085 6085 - # 6086 6086 - # Information about a guest panic 6087 6087 - # 6088 6088 - # Since: 2.9 6089 6089 - ## 6090 6090 - {'union': 'GuestPanicInformation', 6091 6091 - 'base': {'type': 'GuestPanicInformationType'}, 6092 6092 - 'discriminator': 'type', 6093 6093 - 'data': { 'hyper-v': 'GuestPanicInformationHyperV' } } 6094 6094 - 6095 6095 - ## 6096 6096 - # @GuestPanicInformationHyperV: 6097 6097 - # 6098 6098 - # Hyper-V specific guest panic information (HV crash MSRs) 6099 6099 - # 6100 6100 - # Since: 2.9 6101 6101 - ## 6102 6102 - {'struct': 'GuestPanicInformationHyperV', 6103 6103 - 'data': { 'arg1': 'uint64', 6104 6104 - 'arg2': 'uint64', 6105 6105 - 'arg3': 'uint64', 6106 6106 - 'arg4': 'uint64', 6107 6107 - 'arg5': 'uint64' } } 6108 5945 6109 5946 ## 6110 5947 # @rtc-reset-reinjection:

-182

qapi/event.json

··· 5 5 ## 6 6 7 7 ## 8 8 - # @SHUTDOWN: 9 9 - # 10 10 - # Emitted when the virtual machine has shut down, indicating that qemu is 11 11 - # about to exit. 12 12 - # 13 13 - # @guest: If true, the shutdown was triggered by a guest request (such as 14 14 - # a guest-initiated ACPI shutdown request or other hardware-specific action) 15 15 - # rather than a host request (such as sending qemu a SIGINT). (since 2.10) 16 16 - # 17 17 - # Note: If the command-line option "-no-shutdown" has been specified, qemu will 18 18 - # not exit, and a STOP event will eventually follow the SHUTDOWN event 19 19 - # 20 20 - # Since: 0.12.0 21 21 - # 22 22 - # Example: 23 23 - # 24 24 - # <- { "event": "SHUTDOWN", "data": { "guest": true }, 25 25 - # "timestamp": { "seconds": 1267040730, "microseconds": 682951 } } 26 26 - # 27 27 - ## 28 28 - { 'event': 'SHUTDOWN', 'data': { 'guest': 'bool' } } 29 29 - 30 30 - ## 31 31 - # @POWERDOWN: 32 32 - # 33 33 - # Emitted when the virtual machine is powered down through the power control 34 34 - # system, such as via ACPI. 35 35 - # 36 36 - # Since: 0.12.0 37 37 - # 38 38 - # Example: 39 39 - # 40 40 - # <- { "event": "POWERDOWN", 41 41 - # "timestamp": { "seconds": 1267040730, "microseconds": 682951 } } 42 42 - # 43 43 - ## 44 44 - { 'event': 'POWERDOWN' } 45 45 - 46 46 - ## 47 47 - # @RESET: 48 48 - # 49 49 - # Emitted when the virtual machine is reset 50 50 - # 51 51 - # @guest: If true, the reset was triggered by a guest request (such as 52 52 - # a guest-initiated ACPI reboot request or other hardware-specific action) 53 53 - # rather than a host request (such as the QMP command system_reset). 54 54 - # (since 2.10) 55 55 - # 56 56 - # Since: 0.12.0 57 57 - # 58 58 - # Example: 59 59 - # 60 60 - # <- { "event": "RESET", "data": { "guest": false }, 61 61 - # "timestamp": { "seconds": 1267041653, "microseconds": 9518 } } 62 62 - # 63 63 - ## 64 64 - { 'event': 'RESET', 'data': { 'guest': 'bool' } } 65 65 - 66 66 - ## 67 67 - # @STOP: 68 68 - # 69 69 - # Emitted when the virtual machine is stopped 70 70 - # 71 71 - # Since: 0.12.0 72 72 - # 73 73 - # Example: 74 74 - # 75 75 - # <- { "event": "STOP", 76 76 - # "timestamp": { "seconds": 1267041730, "microseconds": 281295 } } 77 77 - # 78 78 - ## 79 79 - { 'event': 'STOP' } 80 80 - 81 81 - ## 82 82 - # @RESUME: 83 83 - # 84 84 - # Emitted when the virtual machine resumes execution 85 85 - # 86 86 - # Since: 0.12.0 87 87 - # 88 88 - # Example: 89 89 - # 90 90 - # <- { "event": "RESUME", 91 91 - # "timestamp": { "seconds": 1271770767, "microseconds": 582542 } } 92 92 - # 93 93 - ## 94 94 - { 'event': 'RESUME' } 95 95 - 96 96 - ## 97 97 - # @SUSPEND: 98 98 - # 99 99 - # Emitted when guest enters a hardware suspension state, for example, S3 state, 100 100 - # which is sometimes called standby state 101 101 - # 102 102 - # Since: 1.1 103 103 - # 104 104 - # Example: 105 105 - # 106 106 - # <- { "event": "SUSPEND", 107 107 - # "timestamp": { "seconds": 1344456160, "microseconds": 309119 } } 108 108 - # 109 109 - ## 110 110 - { 'event': 'SUSPEND' } 111 111 - 112 112 - ## 113 113 - # @SUSPEND_DISK: 114 114 - # 115 115 - # Emitted when guest enters a hardware suspension state with data saved on 116 116 - # disk, for example, S4 state, which is sometimes called hibernate state 117 117 - # 118 118 - # Note: QEMU shuts down (similar to event @SHUTDOWN) when entering this state 119 119 - # 120 120 - # Since: 1.2 121 121 - # 122 122 - # Example: 123 123 - # 124 124 - # <- { "event": "SUSPEND_DISK", 125 125 - # "timestamp": { "seconds": 1344456160, "microseconds": 309119 } } 126 126 - # 127 127 - ## 128 128 - { 'event': 'SUSPEND_DISK' } 129 129 - 130 130 - ## 131 131 - # @WAKEUP: 132 132 - # 133 133 - # Emitted when the guest has woken up from suspend state and is running 134 134 - # 135 135 - # Since: 1.1 136 136 - # 137 137 - # Example: 138 138 - # 139 139 - # <- { "event": "WAKEUP", 140 140 - # "timestamp": { "seconds": 1344522075, "microseconds": 745528 } } 141 141 - # 142 142 - ## 143 143 - { 'event': 'WAKEUP' } 144 144 - 145 145 - ## 146 8 # @RTC_CHANGE: 147 9 # 148 10 # Emitted when the guest changes the RTC time. ··· 163 25 ## 164 26 { 'event': 'RTC_CHANGE', 165 27 'data': { 'offset': 'int' } } 166 166 - 167 167 - ## 168 168 - # @WATCHDOG: 169 169 - # 170 170 - # Emitted when the watchdog device's timer is expired 171 171 - # 172 172 - # @action: action that has been taken 173 173 - # 174 174 - # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is 175 175 - # followed respectively by the RESET, SHUTDOWN, or STOP events 176 176 - # 177 177 - # Note: This event is rate-limited. 178 178 - # 179 179 - # Since: 0.13.0 180 180 - # 181 181 - # Example: 182 182 - # 183 183 - # <- { "event": "WATCHDOG", 184 184 - # "data": { "action": "reset" }, 185 185 - # "timestamp": { "seconds": 1267061043, "microseconds": 959568 } } 186 186 - # 187 187 - ## 188 188 - { 'event': 'WATCHDOG', 189 189 - 'data': { 'action': 'WatchdogExpirationAction' } } 190 28 191 29 ## 192 30 # @DEVICE_DELETED: ··· 489 327 ## 490 328 { 'event': 'BALLOON_CHANGE', 491 329 'data': { 'actual': 'int' } } 492 492 - 493 493 - ## 494 494 - # @GUEST_PANICKED: 495 495 - # 496 496 - # Emitted when guest OS panic is detected 497 497 - # 498 498 - # @action: action that has been taken, currently always "pause" 499 499 - # 500 500 - # @info: information about a panic (since 2.9) 501 501 - # 502 502 - # Since: 1.5 503 503 - # 504 504 - # Example: 505 505 - # 506 506 - # <- { "event": "GUEST_PANICKED", 507 507 - # "data": { "action": "pause" } } 508 508 - # 509 509 - ## 510 510 - { 'event': 'GUEST_PANICKED', 511 511 - 'data': { 'action': 'GuestPanicAction', '*info': 'GuestPanicInformation' } } 512 330 513 331 ## 514 332 # @QUORUM_FAILURE:

+352

qapi/run-state.json

··· 1 1 + # -*- Mode: Python -*- 2 2 + # 3 3 + 4 4 + ## 5 5 + # = VM run state 6 6 + ## 7 7 + 8 8 + ## 9 9 + # @RunState: 10 10 + # 11 11 + # An enumeration of VM run states. 12 12 + # 13 13 + # @debug: QEMU is running on a debugger 14 14 + # 15 15 + # @finish-migrate: guest is paused to finish the migration process 16 16 + # 17 17 + # @inmigrate: guest is paused waiting for an incoming migration. Note 18 18 + # that this state does not tell whether the machine will start at the 19 19 + # end of the migration. This depends on the command-line -S option and 20 20 + # any invocation of 'stop' or 'cont' that has happened since QEMU was 21 21 + # started. 22 22 + # 23 23 + # @internal-error: An internal error that prevents further guest execution 24 24 + # has occurred 25 25 + # 26 26 + # @io-error: the last IOP has failed and the device is configured to pause 27 27 + # on I/O errors 28 28 + # 29 29 + # @paused: guest has been paused via the 'stop' command 30 30 + # 31 31 + # @postmigrate: guest is paused following a successful 'migrate' 32 32 + # 33 33 + # @prelaunch: QEMU was started with -S and guest has not started 34 34 + # 35 35 + # @restore-vm: guest is paused to restore VM state 36 36 + # 37 37 + # @running: guest is actively running 38 38 + # 39 39 + # @save-vm: guest is paused to save the VM state 40 40 + # 41 41 + # @shutdown: guest is shut down (and -no-shutdown is in use) 42 42 + # 43 43 + # @suspended: guest is suspended (ACPI S3) 44 44 + # 45 45 + # @watchdog: the watchdog action is configured to pause and has been triggered 46 46 + # 47 47 + # @guest-panicked: guest has been panicked as a result of guest OS panic 48 48 + # 49 49 + # @colo: guest is paused to save/restore VM state under colo checkpoint, 50 50 + # VM can not get into this state unless colo capability is enabled 51 51 + # for migration. (since 2.8) 52 52 + ## 53 53 + { 'enum': 'RunState', 54 54 + 'data': [ 'debug', 'inmigrate', 'internal-error', 'io-error', 'paused', 55 55 + 'postmigrate', 'prelaunch', 'finish-migrate', 'restore-vm', 56 56 + 'running', 'save-vm', 'shutdown', 'suspended', 'watchdog', 57 57 + 'guest-panicked', 'colo' ] } 58 58 + 59 59 + ## 60 60 + # @StatusInfo: 61 61 + # 62 62 + # Information about VCPU run state 63 63 + # 64 64 + # @running: true if all VCPUs are runnable, false if not runnable 65 65 + # 66 66 + # @singlestep: true if VCPUs are in single-step mode 67 67 + # 68 68 + # @status: the virtual machine @RunState 69 69 + # 70 70 + # Since: 0.14.0 71 71 + # 72 72 + # Notes: @singlestep is enabled through the GDB stub 73 73 + ## 74 74 + { 'struct': 'StatusInfo', 75 75 + 'data': {'running': 'bool', 'singlestep': 'bool', 'status': 'RunState'} } 76 76 + 77 77 + ## 78 78 + # @query-status: 79 79 + # 80 80 + # Query the run status of all VCPUs 81 81 + # 82 82 + # Returns: @StatusInfo reflecting all VCPUs 83 83 + # 84 84 + # Since: 0.14.0 85 85 + # 86 86 + # Example: 87 87 + # 88 88 + # -> { "execute": "query-status" } 89 89 + # <- { "return": { "running": true, 90 90 + # "singlestep": false, 91 91 + # "status": "running" } } 92 92 + # 93 93 + ## 94 94 + { 'command': 'query-status', 'returns': 'StatusInfo' } 95 95 + 96 96 + ## 97 97 + # @SHUTDOWN: 98 98 + # 99 99 + # Emitted when the virtual machine has shut down, indicating that qemu is 100 100 + # about to exit. 101 101 + # 102 102 + # @guest: If true, the shutdown was triggered by a guest request (such as 103 103 + # a guest-initiated ACPI shutdown request or other hardware-specific action) 104 104 + # rather than a host request (such as sending qemu a SIGINT). (since 2.10) 105 105 + # 106 106 + # Note: If the command-line option "-no-shutdown" has been specified, qemu will 107 107 + # not exit, and a STOP event will eventually follow the SHUTDOWN event 108 108 + # 109 109 + # Since: 0.12.0 110 110 + # 111 111 + # Example: 112 112 + # 113 113 + # <- { "event": "SHUTDOWN", "data": { "guest": true }, 114 114 + # "timestamp": { "seconds": 1267040730, "microseconds": 682951 } } 115 115 + # 116 116 + ## 117 117 + { 'event': 'SHUTDOWN', 'data': { 'guest': 'bool' } } 118 118 + 119 119 + ## 120 120 + # @POWERDOWN: 121 121 + # 122 122 + # Emitted when the virtual machine is powered down through the power control 123 123 + # system, such as via ACPI. 124 124 + # 125 125 + # Since: 0.12.0 126 126 + # 127 127 + # Example: 128 128 + # 129 129 + # <- { "event": "POWERDOWN", 130 130 + # "timestamp": { "seconds": 1267040730, "microseconds": 682951 } } 131 131 + # 132 132 + ## 133 133 + { 'event': 'POWERDOWN' } 134 134 + 135 135 + ## 136 136 + # @RESET: 137 137 + # 138 138 + # Emitted when the virtual machine is reset 139 139 + # 140 140 + # @guest: If true, the reset was triggered by a guest request (such as 141 141 + # a guest-initiated ACPI reboot request or other hardware-specific action) 142 142 + # rather than a host request (such as the QMP command system_reset). 143 143 + # (since 2.10) 144 144 + # 145 145 + # Since: 0.12.0 146 146 + # 147 147 + # Example: 148 148 + # 149 149 + # <- { "event": "RESET", "data": { "guest": false }, 150 150 + # "timestamp": { "seconds": 1267041653, "microseconds": 9518 } } 151 151 + # 152 152 + ## 153 153 + { 'event': 'RESET', 'data': { 'guest': 'bool' } } 154 154 + 155 155 + ## 156 156 + # @STOP: 157 157 + # 158 158 + # Emitted when the virtual machine is stopped 159 159 + # 160 160 + # Since: 0.12.0 161 161 + # 162 162 + # Example: 163 163 + # 164 164 + # <- { "event": "STOP", 165 165 + # "timestamp": { "seconds": 1267041730, "microseconds": 281295 } } 166 166 + # 167 167 + ## 168 168 + { 'event': 'STOP' } 169 169 + 170 170 + ## 171 171 + # @RESUME: 172 172 + # 173 173 + # Emitted when the virtual machine resumes execution 174 174 + # 175 175 + # Since: 0.12.0 176 176 + # 177 177 + # Example: 178 178 + # 179 179 + # <- { "event": "RESUME", 180 180 + # "timestamp": { "seconds": 1271770767, "microseconds": 582542 } } 181 181 + # 182 182 + ## 183 183 + { 'event': 'RESUME' } 184 184 + 185 185 + ## 186 186 + # @SUSPEND: 187 187 + # 188 188 + # Emitted when guest enters a hardware suspension state, for example, S3 state, 189 189 + # which is sometimes called standby state 190 190 + # 191 191 + # Since: 1.1 192 192 + # 193 193 + # Example: 194 194 + # 195 195 + # <- { "event": "SUSPEND", 196 196 + # "timestamp": { "seconds": 1344456160, "microseconds": 309119 } } 197 197 + # 198 198 + ## 199 199 + { 'event': 'SUSPEND' } 200 200 + 201 201 + ## 202 202 + # @SUSPEND_DISK: 203 203 + # 204 204 + # Emitted when guest enters a hardware suspension state with data saved on 205 205 + # disk, for example, S4 state, which is sometimes called hibernate state 206 206 + # 207 207 + # Note: QEMU shuts down (similar to event @SHUTDOWN) when entering this state 208 208 + # 209 209 + # Since: 1.2 210 210 + # 211 211 + # Example: 212 212 + # 213 213 + # <- { "event": "SUSPEND_DISK", 214 214 + # "timestamp": { "seconds": 1344456160, "microseconds": 309119 } } 215 215 + # 216 216 + ## 217 217 + { 'event': 'SUSPEND_DISK' } 218 218 + 219 219 + ## 220 220 + # @WAKEUP: 221 221 + # 222 222 + # Emitted when the guest has woken up from suspend state and is running 223 223 + # 224 224 + # Since: 1.1 225 225 + # 226 226 + # Example: 227 227 + # 228 228 + # <- { "event": "WAKEUP", 229 229 + # "timestamp": { "seconds": 1344522075, "microseconds": 745528 } } 230 230 + # 231 231 + ## 232 232 + { 'event': 'WAKEUP' } 233 233 + 234 234 + ## 235 235 + # @WATCHDOG: 236 236 + # 237 237 + # Emitted when the watchdog device's timer is expired 238 238 + # 239 239 + # @action: action that has been taken 240 240 + # 241 241 + # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is 242 242 + # followed respectively by the RESET, SHUTDOWN, or STOP events 243 243 + # 244 244 + # Note: This event is rate-limited. 245 245 + # 246 246 + # Since: 0.13.0 247 247 + # 248 248 + # Example: 249 249 + # 250 250 + # <- { "event": "WATCHDOG", 251 251 + # "data": { "action": "reset" }, 252 252 + # "timestamp": { "seconds": 1267061043, "microseconds": 959568 } } 253 253 + # 254 254 + ## 255 255 + { 'event': 'WATCHDOG', 256 256 + 'data': { 'action': 'WatchdogExpirationAction' } } 257 257 + 258 258 + ## 259 259 + # @WatchdogExpirationAction: 260 260 + # 261 261 + # An enumeration of the actions taken when the watchdog device's timer is 262 262 + # expired 263 263 + # 264 264 + # @reset: system resets 265 265 + # 266 266 + # @shutdown: system shutdown, note that it is similar to @powerdown, which 267 267 + # tries to set to system status and notify guest 268 268 + # 269 269 + # @poweroff: system poweroff, the emulator program exits 270 270 + # 271 271 + # @pause: system pauses, similar to @stop 272 272 + # 273 273 + # @debug: system enters debug state 274 274 + # 275 275 + # @none: nothing is done 276 276 + # 277 277 + # @inject-nmi: a non-maskable interrupt is injected into the first VCPU (all 278 278 + # VCPUS on x86) (since 2.4) 279 279 + # 280 280 + # Since: 2.1 281 281 + ## 282 282 + { 'enum': 'WatchdogExpirationAction', 283 283 + 'data': [ 'reset', 'shutdown', 'poweroff', 'pause', 'debug', 'none', 284 284 + 'inject-nmi' ] } 285 285 + 286 286 + ## 287 287 + # @GUEST_PANICKED: 288 288 + # 289 289 + # Emitted when guest OS panic is detected 290 290 + # 291 291 + # @action: action that has been taken, currently always "pause" 292 292 + # 293 293 + # @info: information about a panic (since 2.9) 294 294 + # 295 295 + # Since: 1.5 296 296 + # 297 297 + # Example: 298 298 + # 299 299 + # <- { "event": "GUEST_PANICKED", 300 300 + # "data": { "action": "pause" } } 301 301 + # 302 302 + ## 303 303 + { 'event': 'GUEST_PANICKED', 304 304 + 'data': { 'action': 'GuestPanicAction', '*info': 'GuestPanicInformation' } } 305 305 + 306 306 + ## 307 307 + # @GuestPanicAction: 308 308 + # 309 309 + # An enumeration of the actions taken when guest OS panic is detected 310 310 + # 311 311 + # @pause: system pauses 312 312 + # 313 313 + # Since: 2.1 (poweroff since 2.8) 314 314 + ## 315 315 + { 'enum': 'GuestPanicAction', 316 316 + 'data': [ 'pause', 'poweroff' ] } 317 317 + 318 318 + ## 319 319 + # @GuestPanicInformationType: 320 320 + # 321 321 + # An enumeration of the guest panic information types 322 322 + # 323 323 + # Since: 2.9 324 324 + ## 325 325 + { 'enum': 'GuestPanicInformationType', 326 326 + 'data': [ 'hyper-v'] } 327 327 + 328 328 + ## 329 329 + # @GuestPanicInformation: 330 330 + # 331 331 + # Information about a guest panic 332 332 + # 333 333 + # Since: 2.9 334 334 + ## 335 335 + {'union': 'GuestPanicInformation', 336 336 + 'base': {'type': 'GuestPanicInformationType'}, 337 337 + 'discriminator': 'type', 338 338 + 'data': { 'hyper-v': 'GuestPanicInformationHyperV' } } 339 339 + 340 340 + ## 341 341 + # @GuestPanicInformationHyperV: 342 342 + # 343 343 + # Hyper-V specific guest panic information (HV crash MSRs) 344 344 + # 345 345 + # Since: 2.9 346 346 + ## 347 347 + {'struct': 'GuestPanicInformationHyperV', 348 348 + 'data': { 'arg1': 'uint64', 349 349 + 'arg2': 'uint64', 350 350 + 'arg3': 'uint64', 351 351 + 'arg4': 'uint64', 352 352 + 'arg5': 'uint64' } }