From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:52596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RIM2D-0001fw-T8 for qemu-devel@nongnu.org; Mon, 24 Oct 2011 11:01:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RIM28-0005sG-BE for qemu-devel@nongnu.org; Mon, 24 Oct 2011 11:01:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32160) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RIM28-0005rx-4J for qemu-devel@nongnu.org; Mon, 24 Oct 2011 11:01:48 -0400 Message-ID: <4EA57DD0.6030803@redhat.com> Date: Mon, 24 Oct 2011 17:01:36 +0200 From: Avi Kivity MIME-Version: 1.0 References: In-Reply-To: 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 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. > As to whether it's possible, I suppose it could be done if a phyical-memory-read > function could be created for it, similar to what I asked about for live analysis > of a guest kernel run on/from the KVM host. We could use the gdb protocol for this. Currently it reads/writes virtual memory, but we could extend the gdbserver command to make these commands apply to physical memory. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.