From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MxO7b-0003JP-Kv
	for qemu-devel@nongnu.org; Mon, 12 Oct 2009 12:51:44 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MxO7W-0003Hu-0p
	for qemu-devel@nongnu.org; Mon, 12 Oct 2009 12:51:41 -0400
Received: from [199.232.76.173] (port=45710 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MxO7U-0003HI-Q4
	for qemu-devel@nongnu.org; Mon, 12 Oct 2009 12:51:37 -0400
Received: from mx1.redhat.com ([209.132.183.28]:34522)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <pbonzini@redhat.com>) id 1MxO7U-0004Ti-AY
	for qemu-devel@nongnu.org; Mon, 12 Oct 2009 12:51:36 -0400
Message-ID: <4AD35E94.2040108@redhat.com>
Date: Mon, 12 Oct 2009 18:51:32 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <12553646851472-git-send-email-lirans@il.ibm.com>
	<4AD354A1.20401@msgid.tls.msk.ru>
In-Reply-To: <4AD354A1.20401@msgid.tls.msk.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH 0/3 v4] Live migration without shared
	storage
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, lirans@il.ibm.com

On 10/12/2009 06:09 PM, Michael Tokarev wrote:
> lirans@il.ibm.com wrote:
>> This series adds support for live migration without shared storage,
>> means copy the storage while migrating. It was tested with KVM.
>> Supports 2 ways to replicate the storage during migration:
>> 1. Complete copy of storage to destination 2. Assuming the storage is
>> cow based, copy only the allocated data, time of the migration will be
>> linear with the amount of allocated data (user responsibility to
>> verify that the same backend file reside on src and destination).
>
> Hmm. How about something like:
>
> migrate exec:"rsync file1 file2 ... remote: && nc remote port"

That can surely work to copy the base files, but it is a task for an 
upper level like libvirt.  For qemu, copying the copy-on-write data is 
enough.

Paolo