diff options
| author | Viktor Prutyanov | 2018-08-29 14:41:25 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2018-10-02 19:09:12 +0200 |
| commit | 3fa2d384c245bcee3a9ecfa11f298b76ea4c9d57 (patch) | |
| tree | e6dc921bb305a9d2eb6f6a2d24dcd6f553856883 /MAINTAINERS | |
| parent | dump: move Windows dump structures definitions (diff) | |
| download | qemu-3fa2d384c245bcee3a9ecfa11f298b76ea4c9d57.tar.gz qemu-3fa2d384c245bcee3a9ecfa11f298b76ea4c9d57.tar.xz qemu-3fa2d384c245bcee3a9ecfa11f298b76ea4c9d57.zip | |
contrib: add elf2dmp tool
elf2dmp is a converter from ELF dump (produced by 'dump-guest-memory') to
Windows MEMORY.DMP format (also know as 'Complete Memory Dump') which can be
opened in WinDbg.
This tool can help if VMCoreInfo device/driver is absent in Windows VM and
'dump-guest-memory -w' is not available but dump can be created in ELF format.
The tool works as follows:
1. Determine the system paging root looking at GS_BASE or KERNEL_GS_BASE
to locate the PRCB structure and finds the kernel CR3 nearby if QEMU CPU
state CR3 is not suitable.
2. Find an address within the kernel image by dereferencing the first
IDT entry and scans virtual memory upwards until the start of the
kernel.
3. Download a PDB matching the kernel from the Microsoft symbol store,
and figure out the layout of certain relevant structures necessary for
the dump.
4. Populate the corresponding structures in the memory image and create
the appropriate dump header.
Signed-off-by: Viktor Prutyanov <viktor.prutyanov@virtuozzo.com>
Message-Id: <1535546488-30208-3-git-send-email-viktor.prutyanov@virtuozzo.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions