[libvirt] [PATCH] man: Clarify virsh vol-clone works within a single pool

[Jiri Denemark]

On Tue, Apr 19, 2016 at 17:35:59 -0400, Cole Robinson wrote:
> virsh vol-clone is expected to clone a volume within a single
> pool; it doesn't work for cloning across pools. Clarify the docs
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1103714
...
> diff --git a/tools/virsh.pod b/tools/virsh.pod
> index 6c9d4ec..e1c0d8e 100644
> --- a/tools/virsh.pod
> +++ b/tools/virsh.pod
> @@ -3530,10 +3530,10 @@ only slightly higher initial disk space usage.
>  =item B<vol-clone> [I<--pool> I<pool-or-uuid>] I<vol-name-or-key-or-path>
>  I<name> [I<--prealloc-metadata>] [I<--reflink>]
>  
> -Clone an existing volume.  Less powerful, but easier to type, version of
> -B<vol-create-from>.
> +Clone an existing volume within the parent pool.  Less powerful,
> +but easier to type, version of B<vol-create-from>.
>  I<--pool> I<pool-or-uuid> is the name or UUID of the storage pool to create

I think you also want to drop " to create" :-)

> -the volume in.
> +that contains the source volume, and will contain the new volume.
>  I<vol-name-or-key-or-path> is the name or key or path of the source volume.
>  I<name> is the name of the new volume.
>  [I<--prealloc-metadata>] preallocate metadata (for qcow2 images which don't

ACK with the small tweak.

Jirka