All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: capturing windows crash dumps
Date: Wed, 19 Aug 2009 09:35:11 -0400	[thread overview]
Message-ID: <20090819133510.GA26154@phenom.dumpdata.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0177CCC1@trantor>

> > > The memory in question could be anything from 64kb (minidump) to the
> > > size of DomU memory (full dump) or somewhere inbetween (kernel
> dump).
> > > I'm normally just interested in the kernel dump which is normally a
> much
> > > more respectable size, but still not the size of memory you can
> easily
> > > find when the system has gone belly up.
> > 
> > Hmm, okay. Could you dump it out over the emulated serial line?
> > 
> 
> The more I look into it the less fond I get of this idea... I already
> use the serial line for other things.

Not being familiar with Windows dumps, but only with Linux kdump (which is basically
a mini-Linux distro running in 64MB - that includes the initrd.img and + RAM space)
which can dump the entire memory on to whatever you want (NFS, disk, USB, etc). 

How does Windows natively/normally do its dump? Is it just dumping the entire memory space
on the local disk? Or do you have to set special flags to do so from the driver?

  parent reply	other threads:[~2009-08-19 13:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  6:47 capturing windows crash dumps James Harper
2009-08-18  7:54 ` Keir Fraser
2009-08-18 10:42   ` James Harper
2009-08-18 12:10     ` Keir Fraser
2009-08-18 12:16       ` James Harper
2009-08-18 13:47         ` Stefano Stabellini
2009-08-18 23:53           ` James Harper
2009-08-19 10:28       ` James Harper
2009-08-19 10:38         ` Paul Durrant
2009-08-19 13:34           ` Stefano Stabellini
2009-08-19 13:35         ` Konrad Rzeszutek Wilk [this message]
2009-08-19 13:47           ` Paul Durrant
2009-08-20  9:56             ` James Harper
2009-08-20 10:22               ` Keir Fraser

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=20090819133510.GA26154@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.