From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53430) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9J0h-0004Hu-OY for qemu-devel@nongnu.org; Tue, 13 Aug 2013 14:08:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9J0Z-0006rY-AV for qemu-devel@nongnu.org; Tue, 13 Aug 2013 14:07:59 -0400 Received: from mail-we0-x233.google.com ([2a00:1450:400c:c03::233]:54383) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9J0Z-0006rL-4W for qemu-devel@nongnu.org; Tue, 13 Aug 2013 14:07:51 -0400 Received: by mail-we0-f179.google.com with SMTP id t57so7024750wes.10 for ; Tue, 13 Aug 2013 11:07:49 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <520A75CE.6020600@redhat.com> Date: Tue, 13 Aug 2013 20:07:10 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <520A58CD.9000404@suse.de> <520A641F.5040608@redhat.com> <520A65BD.3030408@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] QEMU savevm RAM page offsets List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juerg Haefliger Cc: Michael Tokarev , Laszlo Ersek , =?ISO-8859-1?Q?Andreas_F=E4rber?= , qemu-devel@nongnu.org Il 13/08/2013 19:52, Juerg Haefliger ha scritto: > I didn't mean to imply that the savevm format is broken and needed > fixing. I was just wondering if the data is there and I simply hadn't > found it. Upgrading QEMU is not an option at the moment since these > are tightly controlled productions machines. Is it possible to loadvm > a savevm file from 1.0 with 1.6 to then use guest-memory-dump? Yes, it should, but one important thing since 1.0 has been the merger of qemu-kvm and QEMU. What distribution are you using? I know Fedora allows qemu-kvm-1.0 to QEMU-1.6 compatibility, but I don't know about others. Michael Tokarev is the maintainer of the Debian package, so he may be able to answer. Alternatively, you can modify your utility to simply add 512 MB to the addresses above 3.5 GB. Paolo