From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LOiQy-00026R-JS for qemu-devel@nongnu.org; Sun, 18 Jan 2009 19:56:08 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LOiQv-00024C-1z for qemu-devel@nongnu.org; Sun, 18 Jan 2009 19:56:08 -0500 Received: from [199.232.76.173] (port=57291 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LOiQu-000247-W7 for qemu-devel@nongnu.org; Sun, 18 Jan 2009 19:56:05 -0500 Received: from mx20.gnu.org ([199.232.41.8]:7740) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LOiQu-0005X0-Kk for qemu-devel@nongnu.org; Sun, 18 Jan 2009 19:56:04 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LOiQs-0003AG-D2 for qemu-devel@nongnu.org; Sun, 18 Jan 2009 19:56:02 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH] migration: adding migration to/from a file Date: Mon, 19 Jan 2009 00:55:57 +0000 References: <1232324325-25060-1-git-send-email-uril@redhat.com> In-Reply-To: <1232324325-25060-1-git-send-email-uril@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901190055.57922.paul@codesourcery.com> 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 Cc: Uri Lublin On Monday 19 January 2009, Uri Lublin wrote: > Migration to file, reuses migration-to-fd. > Migration from file, uses qemu-fopen directly. > > The saved state-file should be used only once and removed (or used > with -snapshot, or a the disk-image should be copied), as the > disk image is not saved, only the VM state. > > Also there is not point of doing a _live_ migration to file (except > for debugging migration code), so I recommend to stop the VM before > migrating its state to a file. > > An advantage migration-to-file over savevm/loadvm is that for the latter > a qcow2 is a requirement, while the former works for any image-format. Wouldn't it be better to just implement savevm to file? Paul