On 20/01/20 20:12, Eric Blake wrote:
>> +#
>> +# Example:
>> +#
>> +# <- { "event": "GUEST_CRASHLOADED",
>> +# "data": { "action": "run" } }
>> +#
>> +##
>> +{ 'event': 'GUEST_CRASHLOADED',
>> + 'data': { 'action': 'GuestPanicAction', '*info':
>> 'GuestPanicInformation' } }
>> +
>> +##
>> #
zhenwei pi writes:
> Handle bit 1 write, then post event to monitor.
>
> Suggested by Paolo, declear a new event, using GUEST_PANICKED could
> cause upper layers to react by shutting down or rebooting the guest.
>
> In advance for extention, add GuestPanicInformation in event message.
>
> Signed-
On 1/13/20 8:31 PM, zhenwei pi wrote:
Handle bit 1 write, then post event to monitor.
Suggested by Paolo, declear a new event, using GUEST_PANICKED could
cause upper layers to react by shutting down or rebooting the guest.
In advance for extention, add GuestPanicInformation in event message.
S
On 14/01/20 03:31, zhenwei pi wrote:
> +# @info: information about a panic (since 2.9)
Removed this "since 2.9" and queued both patches, thanks.
Paolo
Handle bit 1 write, then post event to monitor.
Suggested by Paolo, declear a new event, using GUEST_PANICKED could
cause upper layers to react by shutting down or rebooting the guest.
In advance for extention, add GuestPanicInformation in event message.
Signed-off-by: zhenwei pi
---
hw/misc/p
Handle bit 1 write, then post event to monitor.
Suggested by Paolo, declear a new event, using GUEST_PANICKED could
cause upper layers to react by shutting down or rebooting the guest.
In advance for extention, add GuestPanicInformation in event message.
Signed-off-by: zhenwei pi
---
hw/misc/p
