diff options
| author | Alejandro Jimenez <alejandro.j.jimenez@oracle.com> | 2020-12-11 17:31:52 -0500 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-12-15 12:51:58 -0500 |
| commit | c753e8e72548493d2a110c0482c4a987a733b033 (patch) | |
| tree | c8830e44baac83400639be1e8ea4bfbd39d91f7b /hw/pci | |
| parent | 2a5ad60b5406daca3658f2a6735318615ee6a116 (diff) | |
| download | qemu-c753e8e72548493d2a110c0482c4a987a733b033.zip qemu-c753e8e72548493d2a110c0482c4a987a733b033.tar.gz qemu-c753e8e72548493d2a110c0482c4a987a733b033.tar.bz2 | |
vl: Add option to avoid stopping VM upon guest panic
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>
Diffstat (limited to 'hw/pci')
0 files changed, 0 insertions, 0 deletions