From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:51561) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rv6TX-0001mC-U5 for qemu-devel@nongnu.org; Wed, 08 Feb 2012 07:18:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rv6TT-0007rW-Dr for qemu-devel@nongnu.org; Wed, 08 Feb 2012 07:18:15 -0500 Received: from mx1.redhat.com ([209.132.183.28]:12905) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rv6TT-0007rO-6F for qemu-devel@nongnu.org; Wed, 08 Feb 2012 07:18:11 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q18CI9iZ005921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 8 Feb 2012 07:18:09 -0500 Message-ID: <4F3267E0.4060005@redhat.com> Date: Wed, 08 Feb 2012 14:17:36 +0200 From: Orit Wasserman MIME-Version: 1.0 References: <73865e0ce364c40e0eb65ec6b22b819d@mail.gmail.com> <4F312854.3080404@redhat.com> <4F312FB6.3080707@redhat.com> In-Reply-To: <4F312FB6.3080707@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH] replication agent module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org On 02/07/2012 04:05 PM, Paolo Bonzini wrote: > On 02/07/2012 02:50 PM, Stefan Hajnoczi wrote: >>> I guess we might need to attach multiple QMP monitors for this to work >>> (one for libvirt, one for the rephub). I'm not sure if there is a >>> fundamental problem with this or if it just needs to be done. >> >> Agreed. You can already query block devices using QMP 'query-block'. >> By adding in-process NBD server support you could then launch an NBD >> server for each volume which you wish to replicate. However, in this >> case it sounds almost like you want the reverse - you could provide an >> NBD server on the rephub and QEMU would mirror writes to it (the NBD >> client code is already in QEMU). > > Yes, this is how we were also planning to do migration without shared storage, right? We originally planned to run ISCSI target . But now that NBD can handle a file chain we can use it too. > > Paolo > >