From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=46099 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGub5-0007nW-LS for qemu-devel@nongnu.org; Tue, 25 May 2010 09:55:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OGuad-0004LQ-Ia for qemu-devel@nongnu.org; Tue, 25 May 2010 09:54:40 -0400 Received: from mail-vw0-f45.google.com ([209.85.212.45]:49463) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OGuad-0004LH-C1 for qemu-devel@nongnu.org; Tue, 25 May 2010 09:54:39 -0400 Received: by vws6 with SMTP id 6so19944vws.4 for ; Tue, 25 May 2010 06:54:38 -0700 (PDT) Message-ID: <4BFBD693.2030108@codemonkey.ws> Date: Tue, 25 May 2010 08:54:27 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC PATCH 1/1] ceph/rbd block driver for qemu-kvm References: <20100519192222.GD61706@ncolin.muc.de> <4BF5A9D2.5080609@codemonkey.ws> <4BF91937.2070801@redhat.com> <87wrutg4dk.wl%morita.kazutaka@lab.ntt.co.jp> <4BFA5D96.3030603@redhat.com> <4BFA696D.2060606@redhat.com> <4BFAD59E.2010706@codemonkey.ws> <4BFB94D9.5080904@redhat.com> <4BFBCDD9.4070104@codemonkey.ws> <4BFBCFB9.6020104@redhat.com> <4BFBD0C6.9000105@codemonkey.ws> <4BFBD261.9040908@redhat.com> In-Reply-To: <4BFBD261.9040908@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, Blue Swirl , ceph-devel@vger.kernel.org, Christian Brunner , MORITA Kazutaka On 05/25/2010 08:36 AM, Avi Kivity wrote: > > We'd need a kernel-level generic snapshot API for this eventually. > >> or (2) implement BUSE to complement FUSE and CUSE to enable proper >> userspace block devices. > > Likely slow due do lots of copying. Also needs a snapshot API. The kernel could use splice. > (ABUSE was proposed a while ago by Zach). > >> If you want to use a block device within qemu, you almost certainly >> want to be able to manipulate it on the host using standard tools >> (like mount and parted) so it stands to reason that addressing this >> in the kernel makes more sense. > > qemu-nbd also allows this. > > This reasoning also applies to qcow2, btw. I know. Regards, Anthony Liguori