All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viktor Prutyanov <viktor.prutyanov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: rkagan@virtuozzo.com, marcandre.lureau@redhat.com,
	dgilbert@redhat.com, armbru@redhat.com,
	Viktor Prutyanov <viktor.prutyanov@virtuozzo.com>
Subject: [Qemu-devel] [PATCH 0/4] dump: add Windows crashdump format
Date: Thu, 17 May 2018 19:23:38 +0300	[thread overview]
Message-ID: <20180517162342.4330-1-viktor.prutyanov@virtuozzo.com> (raw)

Recently a Windows guest driver has been added with the ability to
publish the data needed to produce useful guest dumps on the
hypervisor side.  The data is wrapped in a standard VMCOREINFO
container and is exposed to the hypervisor via FwCfg (see
https://github.com/virtio-win/kvm-guest-drivers-windows/tree/master/fwcfg64)

This patch series extends dump-guest-memory to make use of this data
and generate guest dumps in Windows crashdump format directly in QEMU
(as opposed to postprocessing the traditional ELF dumps).

The first patch in the series is identical to the one posted two weeks
ago with message-id: <20180501132031.13270-1-viktor.prutyanov@virtuozzo.com>.
The rest are various improvements on top of it, making it useful in
situations beyond immediately after a BSOD.

Viktor Prutyanov (4):
  dump: add Windows dump format to dump-guest-memory
  dump: use system context in Windows dump
  dump: add fallback KDBG using in Windows dump
  dump: add Windows live system dump

 Makefile.target |   1 +
 dump.c          |  24 +++-
 hmp-commands.hx |  13 +-
 hmp.c           |   9 +-
 qapi/misc.json  |   5 +-
 win_dump.c      | 385 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 win_dump.h      | 176 ++++++++++++++++++++++++++
 7 files changed, 604 insertions(+), 9 deletions(-)
 create mode 100644 win_dump.c
 create mode 100644 win_dump.h

-- 
2.14.3

             reply	other threads:[~2018-05-17 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 16:23 Viktor Prutyanov [this message]
2018-05-17 16:23 ` [Qemu-devel] [PATCH 1/4] dump: add Windows dump format to dump-guest-memory Viktor Prutyanov
2018-05-17 16:23 ` [Qemu-devel] [PATCH 2/4] dump: use system context in Windows dump Viktor Prutyanov
2018-05-18 14:48   ` [Qemu-devel] [PATCH] fixup! " Viktor Prutyanov
2018-05-17 16:23 ` [Qemu-devel] [PATCH 3/4] dump: add fallback KDBG using " Viktor Prutyanov
2018-05-17 16:23 ` [Qemu-devel] [PATCH 4/4] dump: add Windows live system dump Viktor Prutyanov
2018-05-17 16:34 ` [Qemu-devel] [PATCH 0/4] dump: add Windows crashdump format no-reply
2018-05-17 16:34 ` no-reply
2018-06-04  8:54 ` Viktor Prutyanov
2018-06-22 14:10 ` Roman Kagan
2018-06-27  9:37 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180517162342.4330-1-viktor.prutyanov@virtuozzo.com \
    --to=viktor.prutyanov@virtuozzo.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkagan@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.