From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RSOrK-0002rf-23 for qemu-devel@nongnu.org; Mon, 21 Nov 2011 03:04:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RSOrI-0001Rg-Sf for qemu-devel@nongnu.org; Mon, 21 Nov 2011 03:04:10 -0500 Received: from [222.73.24.84] (port=50972 helo=song.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RSOrH-0001Nl-2K for qemu-devel@nongnu.org; Mon, 21 Nov 2011 03:04:08 -0500 Message-ID: <4ECA0696.2070603@cn.fujitsu.com> Date: Mon, 21 Nov 2011 16:06:46 +0800 From: Wen Congyang MIME-Version: 1.0 References: <4EC373F8.6080300@cn.fujitsu.com> <94fa6b35-8681-45e0-85dd-ffbe2ec95f74@zmail15.collab.prod.int.phx2.redhat.com> <4EC653A4.5010801@web.de> In-Reply-To: <4EC653A4.5010801@web.de> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [RFC] dump memory when host pci device is used by guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Dave Anderson , qemu-devel At 11/18/2011 08:46 PM, Jan Kiszka Write: > On 2011-11-16 14:29, Dave Anderson wrote: >> >> >> ----- Original Message ----- >>> Hi, all >>> >>> 'virsh dump' can not work when host pci device is used by guest. We have >>> discussed this issue here: >>> http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00736.html >>> >>> We have determined to introduce a new command dump to dump memory. >>> The core file's format can be elf. >>> >>> I created a kdump-elf vmcore, and found that it can be used by both >>> crash and gdb: >>> >> From an enterprise/support point of view, the wholesale replacement >> of the current use of the savevm dumpfile format by "virsh dump" with >> this ELF style format would be a *huge* improvement. > > Yes, fully agree. Would be cool if that could actually work for both > crash and gdb. Looking forward! Because the memory size for x86 machine can greater than 4G, so we should create elf64 format core file for 32bit OS. I create a vmcore: the guest OS is 32-bit, and the vmcore is elf64 format. I can use crash to anaylyze it, but gdb can not do the same thing. I create a kdump-elf64 vmcore on 32-bit machine, and gdb still can not anaylyze it. Does gdb support elf64 format core file on x86 box? Thanks Wen Congyang > > Jan >