From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MoIb5-0006uP-0W for qemu-devel@nongnu.org; Thu, 17 Sep 2009 11:08:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MoIb0-0006sR-9x for qemu-devel@nongnu.org; Thu, 17 Sep 2009 11:08:34 -0400 Received: from [199.232.76.173] (port=35038 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MoIb0-0006sL-0X for qemu-devel@nongnu.org; Thu, 17 Sep 2009 11:08:30 -0400 Received: from thoth.sbs.de ([192.35.17.2]:16217) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MoIaz-000343-Dt for qemu-devel@nongnu.org; Thu, 17 Sep 2009 11:08:29 -0400 Message-ID: <4AB250E6.6030900@siemens.com> Date: Thu, 17 Sep 2009 17:08:22 +0200 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 0/3 v3] Live migration without shared storage List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liran Schour Cc: "qemu-devel@nongnu.org" Liran Schour wrote: > Jan Kiszka wrote on 17/09/2009 17:03:04: > >> 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). >> For my understanding: Does it require the use of qcow[2] or does it also >> work with raw images? > > If you call migrate -b it will do a full copy of the disk, > if you call migrate -i it will do incremental copy means that if you have > qcow disk it will copy only the allocated data. The base image should be > identical > in both source and destination. Ah, ok. So this doesn't affect the feasibility, "just" the effort needed for the replication. > >>> Live migration will work as follows: >>> (qemu) migrate -d tcp:0:4444 # for ordinary live migration >>> (qemu) migrate -d -b tcp:0:4444 # for live migration with complete >> storage copy >>> (qemu) migrate -d -i tcp:0:4444 # for live migration with >> incremental storage copy, storage is cow based. >>> The patches are against qemu.git tree >> ...but without signed-off. Are they RFC for now or do you propose them >> for merge? > > I think that RFC is good for now. [RFC][PATCH ...] :) Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux