Trigger a Kernel Panic on Google Compute Engine Instances by NMI method to capture vmcore.

Solution Verified - Updated

Environment

  • Google Cloud Compute
  • Red Hat Enterprise Linux

Issue

  • How to configure Kdump on Compute Engine.
  • How to manually generate vmcore at the time of system hung by using NMI method.

Prerequisites

Resolution

  • Send NMI signal to the RHEL VM by using either the Google Cloud CLI or the Compute Engine API.

  • Example: Using Google Cloud CLI:

    o Google Cloud CLI

      gcloud compute instances send-diagnostic-interrupt VM_NAME --zone=ZONE

    o Replace the following:

          VM_NAME: instance ID or name of the VM that you want to collect vmcore from
      ZONE: the zone where your VM is located

  • Refer the below link for more information on configuration of Kdump on Google Instances and how to use NMI to trigger panic for capturing vmcore.
    Content from cloud.google.com is not included.Collecting core dumps

Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

 

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.