On 2012年06月18日 19:28, Michal Privoznik wrote:
as we support qed format as well. --- tools/virsh.pod | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/virsh.pod b/tools/virsh.pod index 4729127..fce8fef 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -2163,11 +2163,11 @@ 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, vmdk, qed, host_device. =item B<vol-clone> [I<--pool> I<pool-or-uuid>] I<vol-name-or-key-or-path> I<name>
Looks fine, but rng and virsh help need to update too. And it's better to mention it's for file based storage pools. Osier -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list