From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:49231)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S4iSj-0002AS-UV
	for qemu-devel@nongnu.org; Mon, 05 Mar 2012 19:41:29 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S4iSh-00044U-L2
	for qemu-devel@nongnu.org; Mon, 05 Mar 2012 19:41:09 -0500
Received: from mx1.redhat.com ([209.132.183.28]:19816)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S4iSh-00044O-DI
	for qemu-devel@nongnu.org; Mon, 05 Mar 2012 19:41:07 -0500
Date: Mon, 5 Mar 2012 21:41:02 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20120305214102.01899c01@doriath.home>
In-Reply-To: <4F548360.7060502@cn.fujitsu.com>
References: <4F509A00.80207@cn.fujitsu.com> <4F548360.7060502@cn.fujitsu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC][PATCH 00/16 v8] introducing a new,
 dedicated memory dump mechanism
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>, Dave Anderson <anderson@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, Eric Blake <eblake@redhat.com>

On Mon, 05 Mar 2012 17:12:00 +0800
Wen Congyang <wency@cn.fujitsu.com> wrote:

> At 03/02/2012 05:59 PM, Wen Congyang Wrote:
> > 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
> > 
> > The last version is here:
> > http://lists.nongnu.org/archive/html/qemu-devel/2012-02/msg04228.html
> > 
> > We have determined to introduce a new command dump to dump memory. The core
> > file's format can be elf.
> > 
> > Note:
> > 1. The guest should be x86 or x86_64. The other arch is not supported now.
> > 2. If you use old gdb, gdb may crash. I use gdb-7.3.1, and it does not crash.
> > 3. If the OS is in the second kernel, gdb may not work well, and crash can
> >    work by specifying '--machdep phys_addr=xxx' in the command line. The
> >    reason is that the second kernel will update the page table, and we can
> >    not get the page table for the first kernel.
> > 4. The cpu's state is stored in QEMU note. You neet to modify crash to use
> >    it to calculate phys_base.
> > 5. If the guest OS is 32 bit and the memory size is larger than 4G, the vmcore
> >    is elf64 format. You should use the gdb which is built with --enable-64-bit-bfd.
> > 6. This patchset is based on the upstream tree, and apply one patch that is still
> >    in Luiz Capitulino's tree, because I use the API qemu_get_fd() in this patchset.
> > 
> 
> Hi, Jan, Luiz Capitulino
> Do you have any comments?

I haven't had a chance to review it yet, will do in the next few days.