as we support qed format as well.
---
docs/schemas/storagevol.rng | 1 +
tools/virsh.c | 2 +-
tools/virsh.pod | 5 +++--
3 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/docs/schemas/storagevol.rng b/docs/schemas/storagevol.rng
index 8edb877..7a74331 100644
--- a/docs/schemas/storagevol.rng
+++ b/docs/schemas/storagevol.rng
@@ -153,6 +153,7 @@
<value>iso</value>
<value>qcow</value>
<value>qcow2</value>
+ <value>qed</value>
<value>vmdk</value>
<value>vpc</value>
</choice>
diff --git a/tools/virsh.c b/tools/virsh.c
index 4d34d49..1e1de39 100644
--- a/tools/virsh.c
+++ b/tools/virsh.c
@@ -11351,7 +11351,7 @@ static const vshCmdOptDef opts_vol_create_as[] = {
{"allocation", VSH_OT_STRING, 0,
N_("initial allocation size, as scaled integer (default bytes)")},
{"format", VSH_OT_STRING, 0,
- N_("file format type raw,bochs,qcow,qcow2,vmdk")},
+ N_("file format type raw,bochs,qcow,qcow2,qed,vmdk")},
{"backing-vol", VSH_OT_STRING, 0,
N_("the backing volume if taking a snapshot")},
{"backing-vol-format", VSH_OT_STRING, 0,
diff --git a/tools/virsh.pod b/tools/virsh.pod
index 4729127..1a6bef2 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -2163,11 +2163,12 @@ I<capacity> is the size of the volume to be created, as a
scaled integer
I<--allocation> I<size> is the initial size to be allocated in the volume,
also as a scaled integer defaulting to bytes.
I<--format> I<string> is used in file based storage pools to specify the
volume
-file format to use; raw, bochs, qcow, qcow2, vmdk.
+file format to use; raw, bochs, qcow, qcow2, vmdk, qed.
I<--backing-vol> I<vol-name-or-key-or-path> is the source backing
volume to be used if taking a snapshot of an existing volume.
I<--backing-vol-format> I<string> is the format of the snapshot backing
volume;
-raw, bochs, qcow, qcow2, vmdk, host_device.
+raw, bochs, qcow, qcow2, qed, vmdk, host_device. These are, however, meant for
+file based storage pools.
=item B<vol-clone> [I<--pool> I<pool-or-uuid>]
I<vol-name-or-key-or-path>
I<name>
--
1.7.8.5