2013-04-26 05:24:45 +02:00
|
|
|
PVPANIC DEVICE
|
|
|
|
==============
|
|
|
|
|
|
|
|
pvpanic device is a simulated ISA device, through which a guest panic
|
|
|
|
event is sent to qemu, and a QMP event is generated. This allows
|
|
|
|
management apps (e.g. libvirt) to be notified and respond to the event.
|
|
|
|
|
|
|
|
The management app has the option of waiting for GUEST_PANICKED events,
|
|
|
|
and/or polling for guest-panicked RunState, to learn when the pvpanic
|
|
|
|
device has fired a panic event.
|
|
|
|
|
|
|
|
ISA Interface
|
|
|
|
-------------
|
|
|
|
|
|
|
|
pvpanic exposes a single I/O port, by default 0x505. On read, the bits
|
|
|
|
recognized by the device are set. Software should ignore bits it doesn't
|
|
|
|
recognize. On write, the bits not recognized by the device are ignored.
|
|
|
|
Software should set only bits both itself and the device recognize.
|
2020-01-14 03:31:01 +01:00
|
|
|
|
|
|
|
Bit Definition
|
|
|
|
--------------
|
2020-01-14 03:31:02 +01:00
|
|
|
bit 0: a guest panic has happened and should be processed by the host
|
|
|
|
bit 1: a guest panic has happened and will be handled by the guest;
|
|
|
|
the host should record it or report it, but should not affect
|
|
|
|
the execution of the guest.
|
2013-04-26 05:24:45 +02:00
|
|
|
|
|
|
|
ACPI Interface
|
|
|
|
--------------
|
|
|
|
|
|
|
|
pvpanic device is defined with ACPI ID "QEMU0001". Custom methods:
|
|
|
|
|
|
|
|
RDPT: To determine whether guest panic notification is supported.
|
|
|
|
Arguments: None
|
2020-01-14 03:31:02 +01:00
|
|
|
Return: Returns a byte, with the same semantics as the I/O port
|
|
|
|
interface.
|
2013-04-26 05:24:45 +02:00
|
|
|
|
|
|
|
WRPT: To send a guest panic event
|
2020-01-14 03:31:02 +01:00
|
|
|
Arguments: Arg0 is a byte to be written, with the same semantics as
|
|
|
|
the I/O interface.
|
2013-04-26 05:24:45 +02:00
|
|
|
Return: None
|
|
|
|
|
|
|
|
The ACPI device will automatically refer to the right port in case it
|
|
|
|
is modified.
|