From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDEZN-00006p-Gu for qemu-devel@nongnu.org; Mon, 10 Oct 2011 08:03:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDEZK-0002si-QE for qemu-devel@nongnu.org; Mon, 10 Oct 2011 08:02:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20556) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDEZK-0002sN-FJ for qemu-devel@nongnu.org; Mon, 10 Oct 2011 08:02:54 -0400 Date: Mon, 10 Oct 2011 14:00:21 +0200 From: Alon Levy Message-ID: <20111010120021.GA7847@bow.tlv.redhat.com> References: <4E916035.5050906@web.de> <20111009102338.GN16799@amd.home.annexia.org> <4E92568E.2010507@cn.fujitsu.com> <20111010090825.GG9408@redhat.com> <20111010091021.GH9408@redhat.com> <4E92BC34.6090500@siemens.com> <20111010102112.GB2550@bow.tlv.redhat.com> <4E92CD94.4090104@redhat.com> <20111010110444.GQ9408@redhat.com> <4E92D25D.10905@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E92D25D.10905@redhat.com> Subject: [Qemu-devel] windows crash dump header. was: Re: [Question] dump memory when host pci device is used by guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Jan Kiszka , "Richard W.M. Jones" , qemu-devel , Luiz Capitulino On Mon, Oct 10, 2011 at 01:09:17PM +0200, Paolo Bonzini wrote: > On 10/10/2011 01:04 PM, Daniel P. Berrange wrote: > >On Mon, Oct 10, 2011 at 12:48:52PM +0200, Paolo Bonzini wrote: > >>> On 10/10/2011 12:21 PM, Alon Levy wrote: > >>>>> >> A core file would be that format - for direct gdb processing. No > >>>>> >> proprietary re-inventions please. > >>>> > > >>>> >Just a note: A core file to windows core dump file would be nice for > >>>> >windows guest crashes. > >>> > >>> That requires cooperation from a kernel driver in the Windows guest. > >>> The driver must call KeInitializeCrashDumpHeader and write somewhere > >>> the physical address of the buffer. > >That won't be suitable for 'virsh dump' then, because we need this to > >work when the guest OS is in a crashed/non-responsive state, and so > >we cna't rely on talking to it. > > Note that the guest can generate the buffer before it crashes. > Thanks. The contents seem to be undocumented (stubbed in reactos). I did find a link to a tool made for Xen, but it mentions being broken with Windows 2003 (where KeInitializeCrashDumpHeader was introduced). http://www.osronline.com/showThread.CFM?link=203490 > Paolo >