RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

The pvpanic Windows guest driver now supports an IOCTL which returns the crash dump header:
https://github.com/YanVugenfirer/kvm-guest-drivers-windows/commit/17068d58c8ab00699c54f43a88bb85c03fc7c235

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

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.

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.