From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WO6o5-0007QS-AX for qemu-devel@nongnu.org; Thu, 13 Mar 2014 10:40:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WO6nz-0000UD-C1 for qemu-devel@nongnu.org; Thu, 13 Mar 2014 10:40:25 -0400 Received: from lputeaux-656-01-25-125.w80-12.abo.wanadoo.fr ([80.12.84.125]:56131 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WO6nz-0000TY-5x for qemu-devel@nongnu.org; Thu, 13 Mar 2014 10:40:19 -0400 Date: Thu, 13 Mar 2014 15:40:17 +0100 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20140313144017.GA4798@irqsave.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Building QMP in qemu-nbd List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, I want to make qemu-nbd QMP aware so the cloud stack my customer work on = could start lxc containers with qcow2 KVM images and still benefit from the quo= rum and snapshot goodness. Stefan mentioned the nice idea of splitting qapi-schema.json in small fil= es in a subdirectory so qemu-nbd could use only the block related commands. Eric: What do you think of this idea ? Do you have variants of this idea ? Best regards Beno=EEt