[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PATCH v3 0/2] GlusterFS support in QEMU - v3

From: Bharata B Rao
Subject: [Qemu-devel] [PATCH v3 0/2] GlusterFS support in QEMU - v3
Date: Wed, 25 Jul 2012 11:28:06 +0530
User-agent: Mutt/1.5.21 (2010-09-15)


This is the v3 of the patchset to support GlusterFS backend from QEMU.

Apart from cleanups, the major change in this version is to expose all
the gluster configuration options to QEMU user. With this, the gluster
specification looks like this:

-drive file=gluster:server:[port]:[transport]:volname:image
    - Here 'gluster' is the protocol.
    - 'server' 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.
    - 'transport' specifies the transport used to connect to glusterd. This is
      optional and if not specified, socket transport is used.
    - '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.
    Eg 1: -drive file=gluster:server1:0:socket:test:/image
    Eg 2: -drive file=gluster:server1:::test:/image

As I noted during discussions over v2 post, I have gone with colon(:) based
specification. Given that this is anyway going to change with -blockdev, I
would like to go with this unless people strongly favour the URI based

Changes in v3
- New specification to expose all gluster options to QEMU user.
- Added support for bdrv_aio_cancel(), but not really sure how to test
- Many cleanups based on Stefan Hajnoczi's reveiw comments.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]