From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC7Ta-0001ix-T3 for qemu-devel@nongnu.org; Fri, 07 Oct 2011 06:16:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RC7TZ-0003i6-Gn for qemu-devel@nongnu.org; Fri, 07 Oct 2011 06:16:22 -0400 Received: from thoth.sbs.de ([192.35.17.2]:23835) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC7TZ-0003hE-56 for qemu-devel@nongnu.org; Fri, 07 Oct 2011 06:16:21 -0400 Message-ID: <4E8ED167.1000705@siemens.com> Date: Fri, 07 Oct 2011 12:16:07 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E8ECA91.8040409@cn.fujitsu.com> In-Reply-To: <4E8ECA91.8040409@cn.fujitsu.com> Content-Type: text/plain; charset=ISO-8859-1 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: Wen Congyang Cc: qemu-devel , Luiz Capitulino 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. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux