From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34140) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlGzo-00060V-Q5 for qemu-devel@nongnu.org; Fri, 16 May 2014 08:12:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WlGzi-0002Dq-M5 for qemu-devel@nongnu.org; Fri, 16 May 2014 08:12:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:16037) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlGzi-0002Dg-DT for qemu-devel@nongnu.org; Fri, 16 May 2014 08:12:10 -0400 Message-ID: <5375F6D8.3080006@redhat.com> Date: Fri, 16 May 2014 13:30:32 +0200 From: Laszlo Ersek MIME-Version: 1.0 References: <20140516090322.78f174a3@bahia.local> <20140516115158.301d8fc7@bahia.local> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] dump-guest-memory command? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jun Koi , Greg Kurz Cc: "qemu-devel@nongnu.org" On 05/16/14 11:59, Jun Koi wrote: > - is it true that dump-guest-memory just write down physical memory > page, and does not consider the virtual-memory concept? No, it isn't. Basically, "dump-guest-memory" supports two modes of operation, "paging enabled" and "paging disabled". Many (most?) people dump for the "crash" utility, which is super smart, and extra paging info is not needed. For "crash" we just dump the guest-phys memory ranges the way the guest sees them, and that's it; "crash" figures out everything from that. If you want to use "gdb" rather than "crash", or need the guest-virtual addresses in the ELF vmcore for some other reason, then you should invoke "dump-guest-memory" with paging enabled. Enter "help dump-guest-memory" at the qemu monitor prompt, and look for the "-p" option. Laszlo