From 933473e572796c05b99f80d759c4f0e76ea652db Mon Sep 17 00:00:00 2001 From: xiexs Date: Wed, 27 Jan 2016 00:14:46 -0500 Subject: [PATCH] Hypervisor support matrix: add feature "trigger crash dump" The feature triggering crash dump has already been supported by nova [1], now we should complete the support matrix correspondingly. [1]The change id is: Iaf63352139c466430d3304a87a66398133541fac Change-Id: I769cab81ba72d48db259d737cbe5e69f7d530e73 --- doc/source/support-matrix.ini | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/doc/source/support-matrix.ini b/doc/source/support-matrix.ini index 6d96376467d0..b5411b1eba70 100644 --- a/doc/source/support-matrix.ini +++ b/doc/source/support-matrix.ini @@ -544,6 +544,28 @@ driver-impl-ironic=complete driver-impl-libvirt-vz-vm=complete driver-impl-libvirt-vz-ct=complete +[operation.trigger-crash-dump] +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. +cli= +driver-impl-xenserver=missing +driver-impl-libvirt-kvm-x86=complete +driver-impl-libvirt-kvm-ppc64=complete +driver-impl-libvirt-kvm-s390x=complete +driver-impl-libvirt-qemu-x86=complete +driver-impl-libvirt-lxc=missing +driver-impl-libvirt-xen=missing +driver-impl-vmware=missing +driver-impl-hyperv=missing +driver-impl-ironic=missing +driver-impl-libvirt-vz-vm=missing +driver-impl-libvirt-vz-ct=missing + [operation.unpause] title=Resume instance CPUs (unpause) status=optional