QEMU Machine Protocol Events ============================ DUMP_COMPLETED -------------- Emitted when the guest has finished one memory dump. Data: - "result": DumpQueryResult type described in qapi-schema.json - "error": Error message when dump failed. This is only a human-readable string provided when dump failed. It should not be parsed in any way (json-string, optional) Example: { "event": "DUMP_COMPLETED", "data": {"result": {"total": 1090650112, "status": "completed", "completed": 1090650112} } } MEM_UNPLUG_ERROR -------------------- Emitted when memory hot unplug error occurs. Data: - "device": device name (json-string) - "msg": Informative message (e.g., reason for the error) (json-string) Example: { "event": "MEM_UNPLUG_ERROR" "data": { "device": "dimm1", "msg": "acpi: device unplug for unsupported device" }, "timestamp": { "seconds": 1265044230, "microseconds": 450486 } } QUORUM_REPORT_BAD ----------------- Emitted to report a corruption of a Quorum file. Data: - "type": Quorum operation type - "error": Error message (json-string, optional) Only present on failure. This field contains a human-readable error message. There are no semantics other than that the block layer reported an error and clients should not try to interpret the error string. - "node-name": The graph node name of the block driver state. - "sector-num": Number of the first sector of the failed read operation. - "sectors-count": Failed read operation sector count. Example: Read operation: { "event": "QUORUM_REPORT_BAD", "data": { "node-name": "node0", "sector-num": 345435, "sectors-count": 5, "type": "read" }, "timestamp": { "seconds": 1344522075, "microseconds": 745528 } } Flush operation: { "event": "QUORUM_REPORT_BAD", "data": { "node-name": "node0", "sector-num": 0, "sectors-count": 2097120, "type": "flush", "error": "Broken pipe" }, "timestamp": { "seconds": 1456406829, "microseconds": 291763 } } Note: this event is rate-limited. MIGRATION_PASS -------------- Emitted from the source side of a migration at the start of each pass (when it syncs the dirty bitmap) Data: None. - "pass": An incrementing count (starting at 1 on the first pass) Example: {"timestamp": {"seconds": 1449669631, "microseconds": 239225}, "event": "MIGRATION_PASS", "data": {"pass": 2}} VSERPORT_CHANGE --------------- Emitted when the guest opens or closes a virtio-serial port. Data: - "id": device identifier of the virtio-serial port (json-string) - "open": true if the guest has opened the virtio-serial port (json-bool) Example: { "event": "VSERPORT_CHANGE", "data": { "id": "channel0", "open": true }, "timestamp": { "seconds": 1401385907, "microseconds": 422329 } } Note: this event is rate-limited separately for each "id".