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
---
tools/virsh-volume.c | 2 +-
tools/virsh.pod | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/virsh-volume.c b/tools/virsh-volume.c
index 36dd0ed..9cc8e52 100644
--- a/tools/virsh-volume.c
+++ b/tools/virsh-volume.c
@@ -546,7 +546,7 @@ static const vshCmdInfo info_vol_clone[] = {
.data = N_("clone a volume.")
},
{.name = "desc",
- .data = N_("Clone an existing volume.")
+ .data = N_("Clone an existing volume within the parent pool.")
},
{.name = NULL}
};
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
-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
--
2.7.3