Bug 1419537 - Support creating Windows crash dumps host-side
Summary: Support creating Windows crash dumps host-side
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: xiagao
Depends On: 1398633 1493125
Blocks: 1558351
TreeView+ depends on / blocked
Reported: 2017-02-06 13:10 UTC by Ladi Prosek
Modified: 2020-12-29 04:33 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-12-01 07:28:08 UTC
Type: Feature Request
Target Upstream Version:

Attachments (Terms of Use)

Description Ladi Prosek 2017-02-06 13:10:35 UTC
Description of problem:
Windows uses its own format proprietary format of crash dumps (usually kept in files named MEMORY.DMP) which is currently only possible to generate from within the guest when it crashes with a BSOD, Windows is configured the right way, it has enough free disk space, and can boot back up.

Using the documented KeInitializeCrashDumpHeader kernel API, a 3rd party driver can get the crash dump header, which can be combined with the raw memory image host-side to get a valid MEMORY.DMP. This makes it possible to get dumps not only on BSOD, but also out of running Windows instances.

Comment 1 Ladi Prosek 2017-02-06 13:13:40 UTC
The pvpanic Windows guest driver now supports an IOCTL which returns the crash dump header:

The current plan is to use the QEMU guest agent to read the header out of the guest.

Comment 3 Ladi Prosek 2017-03-20 13:04:41 UTC
Bug 1398633 tracks Linux KASLR support work in the virt stack, which is very similar to what we want to do here with Windows. A piece of data needs to be pushed out to the host to be able to consume crash dumps.

Marking as depending on 1398633 for now. There is a high chance that the solution for Linux KASLR will work for Windows guest as well.

Comment 9 RHEL Program Management 2020-12-01 07:28:08 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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