From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:56864)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wencongyang@gmail.com>) id 1RC9W4-000371-QD
	for qemu-devel@nongnu.org; Fri, 07 Oct 2011 08:27:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wencongyang@gmail.com>) id 1RC9W3-00061b-ES
	for qemu-devel@nongnu.org; Fri, 07 Oct 2011 08:27:04 -0400
Received: from mail-qw0-f45.google.com ([209.85.216.45]:45221)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wencongyang@gmail.com>) id 1RC9W3-00061V-Bc
	for qemu-devel@nongnu.org; Fri, 07 Oct 2011 08:27:03 -0400
Received: by qadb10 with SMTP id b10so3462393qad.4
	for <qemu-devel@nongnu.org>; Fri, 07 Oct 2011 05:27:02 -0700 (PDT)
Message-ID: <4E8EEFC8.9040606@gmail.com>
Date: Fri, 07 Oct 2011 20:25:44 +0800
From: Wen Congyang <wencongyang@gmail.com>
MIME-Version: 1.0
References: <4E8ECA91.8040409@cn.fujitsu.com> <4E8ED167.1000705@siemens.com>
In-Reply-To: <4E8ED167.1000705@siemens.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is
 used by guest
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: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Luiz Capitulino <lcapitulino@redhat.com>

于 2011/10/7 18:16, Jan Kiszka 写道:
> On 2011-10-07 11:46, Wen Congyang wrote:
>> Currently, virsh dump uses monitor command migrate to dump guest's memory
>> to file, and we can use crash to analyze the file.
>>
>> Unfortunately, virsh dump can not work if guest uses host pci device. The
>> reason is that the device's status is also needed to migrate to remote machine,
>> and the host pci device's status is not stored in qemu. So it is unmigratable.
>>
>> I think we can  we can add a option to qmp command migrate(eg: skip) to allow
>> the user to skip the check, and this option should be used only when dumping
>> the guest's memory.
>
> Why not simply attach gdb? That works independently of migration.

If qemu has some problem, we can use gdb to debug it. But if guest os 
has problem
(eg:kernel panic and kdump does not work), we should dump guest's memory 
and use
crash to analyze.

Thanks
Wen Congyang


>
> Jan
>