From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L2RXn-00050U-Mh for qemu-devel@nongnu.org; Tue, 18 Nov 2008 09:27:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L2RXl-0004zq-W1 for qemu-devel@nongnu.org; Tue, 18 Nov 2008 09:27:07 -0500 Received: from [199.232.76.173] (port=54417 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L2RXl-0004zl-K4 for qemu-devel@nongnu.org; Tue, 18 Nov 2008 09:27:05 -0500 Received: from wa-out-1112.google.com ([209.85.146.176]:26274) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L2RXl-0007Ix-NC for qemu-devel@nongnu.org; Tue, 18 Nov 2008 09:27:05 -0500 Received: by wa-out-1112.google.com with SMTP id j5so4127421wah.18 for ; Tue, 18 Nov 2008 06:27:03 -0800 (PST) Message-ID: <4922D0AB.3060004@codemonkey.ws> Date: Tue, 18 Nov 2008 08:26:51 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] add file: migration support (r2) References: <20081118030437.GA940@shareable.org> <200811181257.42351.paul@codesourcery.com> In-Reply-To: <200811181257.42351.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; 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 Cc: Charles Duffy Paul Brook wrote: > On Tuesday 18 November 2008, Jamie Lokier wrote: > >> Paul Brook wrote: >> >>>> I'm not sure if "live" migration to a file is really useful. "Dead" >>>> migration is useful for suspending a VM to disk. >>>> >>> Right. That's the point I was trying to make. >>> >> I thought of a use for live migration to and from a file. It's when >> you have to restart a host while minimising downtime of all its >> guests. The liveness reduces that downtime. >> > > I wouldn't be surprised if this actually took longer, because you have to read > more data in when you do the restore. > file: migration is essentially live checkpointing. It takes longer to save but the key is that you do the checkpointing without incurring down time. The real use case would be live migrating to a file (or BDRV) and then immediately resuming the source VM after the migration has completed. The effect would be live checkpointing. But without an implementation of file: or bdrv: that are actually live, it really is just an academic conversation :-) Regards, Anthony Liguori > Paul > > >