Merge "Documentation fix regarding triggering crash dump"
This commit is contained in:
commit
ec04d3bcaf
@ -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
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user