From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53720) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RIMU1-0004i8-HM for qemu-devel@nongnu.org; Mon, 24 Oct 2011 11:30:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RIMTy-0003EM-Uw for qemu-devel@nongnu.org; Mon, 24 Oct 2011 11:30:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:10603) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RIMTy-0003EA-IK for qemu-devel@nongnu.org; Mon, 24 Oct 2011 11:30:34 -0400 Message-ID: <4EA58488.50306@redhat.com> Date: Mon, 24 Oct 2011 17:30:16 +0200 From: Avi Kivity MIME-Version: 1.0 References: <54c9dc1d-3104-4f42-9a20-d7f4da516bdc@zmail05.collab.prod.int.phx2.redhat.com> In-Reply-To: <54c9dc1d-3104-4f42-9a20-d7f4da516bdc@zmail05.collab.prod.int.phx2.redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dave Anderson Cc: Jan Kiszka , "Richard W.M. Jones" , qemu-devel , Luiz Capitulino , KAMEZAWA Hiroyuki On 10/24/2011 05:25 PM, Dave Anderson wrote: > > ----- Original Message ----- > > On 10/24/2011 04:25 PM, Dave Anderson wrote: > > > > The question is that: 'virsh dump' can not be used when host pci device > > > > is used by guest. We are discussing how to fix the problem. We have determined > > > > that introduce a new monitor command dump. Jan suggested that the core file's > > > > format is gdb standard core format. Does crash support such format? If no, > > > > is it possible to support such format? > > > > > > If you are talking about an ELF core dump of the user-space qemu-kvm process > > > running on the host, then it's certainly not supported. > > > > No, an ELF image of the guest's physical memory. > > Well then that should be pretty straight forward to support. Depending upon > how similar it would be to the "standard" kdump ELF format, the only other > issue is how to determine the physical base address at which the kernel is > loaded, in order to be able to translate the mapped kernel-text/static-data > virtual region of the x86_64 arch (the __START_KERNEL_map region). > I guess an elf note would work for that? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.