Bug 2232641 - What files are needed to read memory dump
Summary: What files are needed to read memory dump
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.13.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 4.13.4
Assignee: skagan
QA Contact: Natalie Gavrielov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 17:25 UTC by Bill Bell
Modified: 2023-09-05 17:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-05 17:18:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-32214 0 None None None 2023-08-17 17:29:26 UTC

Description Bill Bell 2023-08-17 17:25:56 UTC
Description of problem: 

I am currently writing a blog and am looking to find out what files are needed to successfully read a memory dump for a rhel 9 vm that was generated using the "virtctl memory-dump" tool. I have tried to read multiple linux memory dumps using volatility3 and gdb and have gotten anything from "not a valid memory dump" to it showing no processes. Information on the tool does not contain this info.

Comment 1 Bill Bell 2023-09-05 17:18:22 UTC
I was able to resolve this by working with the volatility admins. It seems that none of the tools I used saw the file as valid memory dump unless I exported it as a *.dump.tar.gz file. It may not be necessary to tar the dump file, but the format of the vmexport output file isn't noted in the official documentation listed below.

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html/virtualization/virt-using-the-cli-tools#vm-memory-dump-commands_virt-using-the-cli-tools


Note You need to log in before you can comment on or make changes to this bug.