From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC70n-0005Sa-NF for qemu-devel@nongnu.org; Fri, 07 Oct 2011 05:46:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RC70m-0006kH-M5 for qemu-devel@nongnu.org; Fri, 07 Oct 2011 05:46:37 -0400 Received: from [222.73.24.84] (port=56245 helo=song.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC70l-0006jX-W1 for qemu-devel@nongnu.org; Fri, 07 Oct 2011 05:46:36 -0400 Message-ID: <4E8ECA91.8040409@cn.fujitsu.com> Date: Fri, 07 Oct 2011 17:46:57 +0800 From: Wen Congyang MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Subject: [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: qemu-devel , Luiz Capitulino 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. Thanks Wen Congyang