From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:45588)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1Rnioz-0003Kz-Ks
	for qemu-devel@nongnu.org; Wed, 18 Jan 2012 22:37:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1Rnioy-0004oi-11
	for qemu-devel@nongnu.org; Wed, 18 Jan 2012 22:37:53 -0500
Received: from [222.73.24.84] (port=51811 helo=song.cn.fujitsu.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1Rniox-0004oe-Io
	for qemu-devel@nongnu.org; Wed, 18 Jan 2012 22:37:51 -0500
Message-ID: <4F17907E.4070302@cn.fujitsu.com>
Date: Thu, 19 Jan 2012 11:39:42 +0800
From: Wen Congyang <wency@cn.fujitsu.com>
MIME-Version: 1.0
References: <4F1784EE.2040800@cn.fujitsu.com>
	<CA+g7VZ28PREzujUS30=7pMj5dvAHJkpWPjfdrwVcrMgbVxdY7w@mail.gmail.com>
In-Reply-To: <CA+g7VZ28PREzujUS30=7pMj5dvAHJkpWPjfdrwVcrMgbVxdY7w@mail.gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Qemu-devel] [RFC][PATCH 00/15 v5] 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: Jun Koi <junkoi2004@gmail.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>, Luiz Capitulino <lcapitulino@redhat.com>

At 01/19/2012 11:32 AM, Jun Koi Wrote:
> On Thu, Jan 19, 2012 at 10:50 AM, Wen Congyang <wency@cn.fujitsu.com> 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
>>
>> We have determined to introduce a new command dump to dump memory. The core
>> file's format can be elf.
> 
> do you pause the guest when the dump happen, or you can somehow let it
> continue to run?

I pause the guest when the dump happens.

> 
> would be wonderful if you can do the latter, since dumping a guest
> memory can take a lot of time.

Yes, it may tak a lot of time. But we dump a guest memory when the guest
panics, and there is no need to continue to run the guest.

Thanks
Wen Congyang

> 
> thanks,
> Jun
>