From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44882) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T3NH6-0001X8-6P for qemu-devel@nongnu.org; Mon, 20 Aug 2012 04:23:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T3NH5-00034v-6u for qemu-devel@nongnu.org; Mon, 20 Aug 2012 04:23:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:14391) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T3NH4-00034q-V1 for qemu-devel@nongnu.org; Mon, 20 Aug 2012 04:23:51 -0400 Message-ID: <5031F411.4020105@redhat.com> Date: Mon, 20 Aug 2012 10:23:45 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1344951151-26387-1-git-send-email-aliguori@us.ibm.com> <20120814144227.GB10909@stefanha-thinkpad.localdomain> <20120815123806.GB4214@stefanha-thinkpad.localdomain> <502FE81B.3060006@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] block-migration: deprecate block migration for the 1.2 release List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ruben Kerkhof Cc: Kevin Wolf , Anthony Liguori , Stefan Hajnoczi , qemu-devel@nongnu.org Il 19/08/2012 10:13, Ruben Kerkhof ha scritto: >> > That's correct. Live block migration will use two ports, both served by >> > the destination, one using NBD and one for RAM/device migration data. >> > It will be a little more complicated than just migrate -b, but nothing >> > that libvirt cannot orchestrate. > Will I still be able to cap the migration bandwidth? Yes, though you will have to cap the two bandwidths separately. > And how about security? Libvirt can tunnel the data, I believe by > passing an fd to qemu, and encrypting the connection with TLS. Libvirt can do the same on the NBD connection. Paolo