From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KnJ4y-0003a1-Uz for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:22:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KnJ4y-0003Zm-G5 for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:22:48 -0400 Received: from [199.232.76.173] (port=39182 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KnJ4y-0003Zj-Br for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:22:48 -0400 Received: from qw-out-1920.google.com ([74.125.92.145]:57432) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KnJ4y-0004C1-0W for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:22:48 -0400 Received: by qw-out-1920.google.com with SMTP id 5so781405qwc.4 for ; Tue, 07 Oct 2008 13:22:47 -0700 (PDT) Message-ID: <48EBC514.7010209@codemonkey.ws> Date: Tue, 07 Oct 2008 15:22:44 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Snapshots not bound to an architecture? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Blue Swirl wrote: > Hi, > > While testing the savevm/loadvm functions, I noticed that it's > possible to attempt to load a snapshot made for entirely different > architecture. There are a lot of warnings, of course. > > Could we prevent this somehow? Or is there a use case for this, for > example loading a snapshot made on i386 to an x86_64 emulator? > I think we should introduce a machine section for save/restore that included that information. It should also be versioned in such a way that it could be incremented whenever a new piece of hardware is added to the default machine type. Regards, Anthony Liguori