openstack
/
nova
Code Issues Proposed changes

Documentation fix regarding triggering crash dump 

How to trigger crash dump depends on hypervisors. NMI is not the only way to
implement the feature. This patch modifies description regarding this feature.

Change-Id: I77d10551650776c06ee4b413f1b027abf6620e83
This commit is contained in:
Hironori Shiina 2016-03-04 12:54:35 +09:00
parent 2c732aa654
commit 230958c002
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-guide/source/server_concepts.rst
View File

@ -556,7 +556,7 @@ Server actions
Trigger crash dump usually utilized by either administrator or the server's
owner, it will dump the memory image as dump file into the given server,
and then reboot the kernel again. And this feature depends on the setting
about the NMI in the server.
about the trigger (e.g. NMI) in the server.
Server passwords
~~~~~~~~~~~~~~~~

8
doc/source/support-matrix.ini
View File

@ -548,10 +548,10 @@ driver-impl-libvirt-vz-ct=complete
title=Trigger crash dump
status=optional
notes=The trigger crash dump operation is a mechanism for triggering
a crash dump in an instance by injecting an NMI (Non-maskable Interrupt)
into the instance. It provides a means to dump the production memory image
as a dump file which is useful for users. Therefore this operation is
considered optional to support.
a crash dump in an instance. The feature is typically implemented by
injecting an NMI (Non-maskable Interrupt) into the instance. It provides
a means to dump the production memory image as a dump file which is useful
for users. Therefore this operation is considered optional to support.
cli=
driver-impl-xenserver=missing
driver-impl-libvirt-kvm-x86=complete