Deepak,
I know that I am not relating to your main issue (sorry...), but...
I like the idea of a hook mangling qemu:commandline.
Could you (or someone else) contribute such a hook to upstream vdsm?
I'm sure many would thank a hook accepting general qemu command line as
custom property, and pass
On 07/16/2012 04:07 PM, Deepak C Shetty wrote:
I am sure VDSM hook is not the ideal way to add this functionality in
VDSM, would request inputs from experts on this list on
what would be a better way in VDSM to exploit QEMU-GlusterFS native
integration ? Ideally based on the Storage Domain type
On 07/29/2012 03:47 PM, Dan Kenigsberg wrote:
Deepak,
I know that I am not relating to your main issue (sorry...), but...
I like the idea of a hook manglingqemu:commandline.
Could you (or someone else) contribute such a hook to upstream vdsm?
I'm sure many would thank a hook accepting general
(top posting)
Hello All,
I am posting a VDSM hook example that helps exploit the
QEMU-GlusterFS native integration from VDSM.
Since the last time i posted on this thread, there are some changes to
the GlusterFS based image/file specification for QEMU.
This was done based on the
Hello All,
Any updates/comments on this mail, anybody ?
More comments/questions inline below
'would appreciate response which can help me here.
thanx,
deepak
On 06/27/2012 06:44 PM, Deepak C Shetty wrote:
Hello,
Recently there were patches posted in qemu-devel to support
gluster
Hello,
Recently there were patches posted in qemu-devel to support gluster
as a block backend for qemu.
This introduced new way of specifying drive location to qemu as ...
-drive file=gluster:volumefile:image name
where...
volumefile is the gluster volume file name ( say gluster
