From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:51354) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RCp5A-0000QG-AR for qemu-devel@nongnu.org; Sun, 09 Oct 2011 04:50:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RCp59-0001co-2F for qemu-devel@nongnu.org; Sun, 09 Oct 2011 04:50:04 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:47299) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RCp58-0001ca-Nr for qemu-devel@nongnu.org; Sun, 09 Oct 2011 04:50:03 -0400 Message-ID: <4E916035.5050906@web.de> Date: Sun, 09 Oct 2011 10:49:57 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E8ECA91.8040409@cn.fujitsu.com> <4E8ED167.1000705@siemens.com> <20111008151622.GA17181@amd.home.annexia.org> In-Reply-To: <20111008151622.GA17181@amd.home.annexia.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig749F417CFA60622D5E7D642A" Sender: jan.kiszka@web.de 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: "Richard W.M. Jones" Cc: qemu-devel , Luiz Capitulino This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig749F417CFA60622D5E7D642A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-10-08 17:16, Richard W.M. Jones wrote: > On Fri, Oct 07, 2011 at 12:16:07PM +0200, Jan Kiszka wrote: >> On 2011-10-07 11:46, Wen Congyang wrote: >>> Currently, virsh dump uses monitor command migrate to dump guest's me= mory >>> 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 remot= e machine, >>> and the host pci device's status is not stored in qemu. So it is unmi= gratable. >>> >>> 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. >=20 > It's a lot more hairy and requires dev tools to be installed on the > production host. >=20 > The core file is technically simple, has no dependencies, can be moved > to another machine for analysis, and contains all the data (not just a > backtrace). As explained in the other replies: It is way more future-proof to use an interface for this which was designed for it (remote gdb) instead of artificially relaxing reasonable constraints of the migration mechanism plus having to follow that format with the post-processing tool. Jan --------------enig749F417CFA60622D5E7D642A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6RYDgACgkQitSsb3rl5xQSuACfW9CbxRRkUKfafoor84n6yczh D5IAoJe5V58JwSvaeVCm9VdEEXM7MORV =zJ+2 -----END PGP SIGNATURE----- --------------enig749F417CFA60622D5E7D642A--