From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mxcat-0007Zt-7f
	for qemu-devel@nongnu.org; Tue, 13 Oct 2009 04:18:55 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mxcao-0007Vi-Rn
	for qemu-devel@nongnu.org; Tue, 13 Oct 2009 04:18:54 -0400
Received: from [199.232.76.173] (port=57556 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mxcao-0007VX-KZ
	for qemu-devel@nongnu.org; Tue, 13 Oct 2009 04:18:50 -0400
Received: from mx1.redhat.com ([209.132.183.28]:13707)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <pbonzini@redhat.com>) id 1Mxcao-0006Jq-3P
	for qemu-devel@nongnu.org; Tue, 13 Oct 2009 04:18:50 -0400
Message-ID: <4AD437E5.2060607@redhat.com>
Date: Tue, 13 Oct 2009 10:18:45 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 0/3 v4] Live migration without shared
	storage
References: <OF6E792584.2B56D7A3-ONC225764E.002BE6F5-C225764E.002D145F@il.ibm.com>
In-Reply-To: <OF6E792584.2B56D7A3-ONC225764E.002BE6F5-C225764E.002D145F@il.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Liran Schour <LIRANS@il.ibm.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org

>>> 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.
>
> I agree that it can be useful to let an upper level component to copy the
> storage
> but you will need a way to synchronize with that layer: 1. qemu -->  upper
> layer:
> vm suspended,no more writes to disk.
> 2. upper layer -->  qemu: storage replication is done.
> I don't see how without it you will have a valid copy of the storage.
>
> However make use of the copy on write data and cut the amount of
> transferred data
> can be done only from inside qemu.

Yes, I understand the reason for this feature.  What I meant was that 
you could use rsync to copy the base files from an upper level 
component, before the actual migration is started and qemu transfers the 
copy-on-write data live.

If Michael was saying instead "why is this needed at all", then you 
answered him.

Paolo