From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Durrant Subject: Re: capturing windows crash dumps Date: Wed, 19 Aug 2009 14:47:07 +0100 Message-ID: <4A8C025B.7000608@citrix.com> References: <20090819133510.GA26154@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090819133510.GA26154@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: James Harper , "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org Konrad Rzeszutek Wilk wrote: > > 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? > Yes, it normally dumps it's memory to the device using a special incarnation of the driver stack for that device. Paul -- =============================== Paul Durrant, Software Engineer Citrix Systems (R&D) Ltd. First Floor, Building 101 Cambridge Science Park Milton Road Cambridge CB4 0FY United Kingdom ===============================