From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:49255) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RD9rh-0005S7-0B for qemu-devel@nongnu.org; Mon, 10 Oct 2011 03:01:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RD9rf-0002Us-9T for qemu-devel@nongnu.org; Mon, 10 Oct 2011 03:01:32 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:45273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RD9re-0002UX-TT for qemu-devel@nongnu.org; Mon, 10 Oct 2011 03:01:31 -0400 Message-ID: <4E929848.6030105@web.de> Date: Mon, 10 Oct 2011 09:01:28 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E8ECA91.8040409@cn.fujitsu.com> <4E8ED167.1000705@siemens.com> <20111008151622.GA17181@amd.home.annexia.org> <4E916035.5050906@web.de> <20111009102338.GN16799@amd.home.annexia.org> <4E92568E.2010507@cn.fujitsu.com> <4E929618.4040403@web.de> <4E9297CB.8010303@cn.fujitsu.com> In-Reply-To: <4E9297CB.8010303@cn.fujitsu.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE35E727D7E0FFE638DD9A3F5" 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: Wen Congyang Cc: Luiz Capitulino , "Richard W.M. Jones" , qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE35E727D7E0FFE638DD9A3F5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2011-10-10 08:59, Wen Congyang wrote: > At 10/10/2011 02:52 PM, Jan Kiszka Write: >> On 2011-10-10 04:21, Wen Congyang wrote: >>> At 10/09/2011 06:23 PM, Richard W.M. Jones Write: >>>> On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote: >>>>> As explained in the other replies: It is way more future-proof to u= se an >>>>> interface for this which was designed for it (remote gdb) instead o= f >>>>> artificially relaxing reasonable constraints of the migration mecha= nism >>>>> plus having to follow that format with the post-processing tool. >>>> >>>> Any interface that isn't "get this information off my production >>>> server *now*" so that I can get the server restarted, and send it to= >>>> an expert to analyse -- is a poor interface, whether it was designed= >>>> like that or not. Perhaps we don't have the right interface at all,= >>>> but remote gdb is not it. >>> >>> What about the following idea? >>> >>> Introduce a new monitor command named dump, and this command accepts = a filename. >>> We can use almost all migration's code. We use this command to dump g= uest's >>> memory, so there is no need to check whether the guest has a unmigrat= able device. >> >> I do not want to reject this proposal categorically, but I would like = to >> see the gdb path fail /wrt essential requirements first. So far I don'= t >> see it would. >=20 > =91gdb path fail /wrt essential requirements=92 >=20 > what does it mean? That you explain why reading reading memory and processor states via the remote gdb interface and dumping it into a proper core file cannot be made working for you. Jan --------------enigE35E727D7E0FFE638DD9A3F5 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/ iEYEARECAAYFAk6SmEgACgkQitSsb3rl5xRN+QCbBm1Yb1N2xSAtIwTaAbvcDgRL FxsAn3Ot8EPkaKn6DwfnxXQqPtdCLbHC =MunT -----END PGP SIGNATURE----- --------------enigE35E727D7E0FFE638DD9A3F5--