From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37421) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TCTkR-0007QC-Fd for qemu-devel@nongnu.org; Fri, 14 Sep 2012 07:07:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TCTkL-0005zu-NX for qemu-devel@nongnu.org; Fri, 14 Sep 2012 07:07:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56426) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TCTkL-0005zm-Ff for qemu-devel@nongnu.org; Fri, 14 Sep 2012 07:07:41 -0400 Message-ID: <50530FF5.6080401@redhat.com> Date: Fri, 14 Sep 2012 13:07:33 +0200 From: Kevin Wolf MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Selective block migration (still on 0.13) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christian Theune Cc: qemu-devel@nongnu.org Am 13.09.2012 16:58, schrieb Christian Theune: > Hi, > > we're currently still on 0.13, looking forward to a large update soon. :) > > We haven't been using live migration up until now, but are > investigating it to multiple downtimes (restarting updated hosts and > restarting updated guests) when doing system updates. So, we're trying > to find out whether we can get this into a usable shape while still > running 0.13. > > I saw that 0.13 does have block migration available. However, looking > at the code, it's an "either or" situation: migrate all block devices > or none. And I advise you to choose "none" with 0.13. While the 1.2 block migration code doesn't add new options over 0.13 and is deprecated, it's expected to kind of work. However, I'm pretty sure that we fixed some data corruptions issues after 0.13 and so I'd expect that 0.13 eats your data when using block migration. Kevin