mirror of
https://github.com/qemu/qemu.git
synced 2024-12-17 17:23:52 +08:00
c753e8e725
The current default action of pausing a guest after a panic event is received leaves the responsibility to resume guest execution to the management layer. The reasons for this behavior are discussed here: https://lore.kernel.org/qemu-devel/52148F88.5000509@redhat.com/ However, in instances like the case of older guests (Linux and Windows) using a pvpanic device but missing support for the PVPANIC_CRASHLOADED event, and Windows guests using the hv-crash enlightenment, it is desirable to allow the guests to continue running after sending a PVPANIC_PANICKED event. This allows such guests to proceed to capture a crash dump and automatically reboot without intervention of a management layer. Add an option to avoid stopping a VM after a panic event is received, by passing: -action panic=none in the command line arguments, or during runtime by using an upcoming QMP command. Suggested-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Alejandro Jimenez <alejandro.j.jimenez@oracle.com> Message-Id: <1607705564-26264-3-git-send-email-alejandro.j.jimenez@oracle.com> [Do not fix panic action in the variable, instead modify -no-shutdown. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
20 lines
456 B
C
20 lines
456 B
C
/*
|
|
* Copyright (c) 2020 Oracle and/or its affiliates.
|
|
*
|
|
* This work is licensed under the terms of the GNU GPL, version 2.
|
|
* See the COPYING file in the top-level directory.
|
|
*
|
|
*/
|
|
|
|
#ifndef RUNSTATE_ACTION_H
|
|
#define RUNSTATE_ACTION_H
|
|
|
|
#include "qapi/qapi-commands-run-state.h"
|
|
|
|
/* in softmmu/runstate-action.c */
|
|
extern RebootAction reboot_action;
|
|
extern ShutdownAction shutdown_action;
|
|
extern PanicAction panic_action;
|
|
|
|
#endif /* RUNSTATE_ACTION_H */
|