From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51806) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SsZLn-0003KP-9l for qemu-devel@nongnu.org; Sat, 21 Jul 2012 09:04:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SsZLm-00070S-DU for qemu-devel@nongnu.org; Sat, 21 Jul 2012 09:04:03 -0400 Received: from e23smtp04.au.ibm.com ([202.81.31.146]:38293) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SsZLl-00070A-Ro for qemu-devel@nongnu.org; Sat, 21 Jul 2012 09:04:02 -0400 Received: from /spool/local by e23smtp04.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sat, 21 Jul 2012 23:03:48 +1000 Received: from d23av02.au.ibm.com (d23av02.au.ibm.com [9.190.235.138]) by d23relay05.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q6LCteVo2294142 for ; Sat, 21 Jul 2012 22:55:40 +1000 Received: from d23av02.au.ibm.com (loopback [127.0.0.1]) by d23av02.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q6LD3rGd003433 for ; Sat, 21 Jul 2012 23:03:53 +1000 Date: Sat, 21 Jul 2012 18:34:46 +0530 From: Bharata B Rao Message-ID: <20120721130446.GG1046@in.ibm.com> References: <20120721082917.GC1046@in.ibm.com> <500A9F23.4090806@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <500A9F23.4090806@redhat.com> Subject: Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 Reply-To: bharata@linux.vnet.ibm.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vijay Bellur Cc: Anand Avati , Amar Tumballi , qemu-devel@nongnu.org On Sat, Jul 21, 2012 at 05:52:59PM +0530, Vijay Bellur wrote: > On 07/21/2012 01:59 PM, Bharata B Rao wrote: > >We now > >specify the gluster backed image like this: > > > >-drive file=gluster:server@port:volname:image > > > >- Here 'gluster' is the protocol. > >- 'server@port' specifies the server where the volume file specification for > > the given volume resides. 'port' is the port number on which gluster > > management daemon (glusterd) is listening. This is optional and if not > > specified, QEMU will send 0 which will make libgfapi to use the default > > port. > >- 'volname' is the name of the gluster volume which contains the VM image. > >- 'image' is the path to the actual VM image in the gluster volume. > > > >Note that we are no longer using volfiles directly and use volume names > >instead. For this to work, gluster management daemon (glusterd) needs to > >be running on the QEMU node. > > > glusterd needs to be running on the server that is specified in > 'server@port' option. oh yes, thanks. > > > > >Scenarios > >--------- > >Base: QEMU boots from directly from image on gluster brick. > >Fuse mount: QEMU boots from VM image on gluster FUSE mount. > >Fuse bypass: QEMU uses gluster protocol and uses standard client volfile. > >Fuse bypass custom: QEMU uses gluster protocol and uses a minimal client > > volfile that just has client xlator. > >RPC bypass: QEMU uses just posix xlator and doesn't depend on gluster server. > > > > For the Fuse mount, Fuse bypass and Fuse bypass custom scenarios, I > assume a single local gluster brick is being used. Is this correct? Right, fio numbers are for single local gluster brick scenario. Regards, Bharata.