Red Hat Bugzilla – Bug 830057
man doc of vol-create-as format is lack of qed and vmdk
Last modified: 2013-09-08 20:03:37 EDT
Description of problem:
vol-create-as format is lack of qed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# man virsh
vol-create-as pool-or-uuid name capacity [--allocation size] [--format
string] [--backing-vol vol-name-or-key-or-path] [--backing-vol-format
Create a volume from a set of arguments. pool-or-uuid is the name
or UUID of the storage pool to create the volume in. name is the
name of the new volume. capacity is the size of the volume to be
created, as a scaled integer (see NOTES above), defaulting to bytes
if there is no suffix. --allocation size is the initial size to be
allocated in the volume, also as a scaled integer defaulting to
bytes. --format string is used in file based storage pools to
specify the volume file format to use; raw, bochs, qcow, qcow2, ----> need add vmdk and qed
vmdk. --backing-vol vol-name-or-key-or-path is the source backing
volume to be used if taking a snapshot of an existing volume.
--backing-vol-format string is the format of the snapshot backing
volume; raw, bochs, qcow, qcow2, vmdk, host_device. ------> need add qed
vol-create-as format is lack of qed and vmdk
Add qed and vmdk
Patch proposed upstream:
Moving to POST:
Author: Michal Privoznik <email@example.com>
AuthorDate: Mon Jun 18 13:20:01 2012 +0200
Commit: Michal Privoznik <firstname.lastname@example.org>
CommitDate: Mon Jun 18 14:40:32 2012 +0200
virsh: Update vol-create-as manpage
as we support qed format as well.
1: #man virsh
is used in file based storage pools to specify the volume file format to use; raw, bochs, qcow, qcow2, vmdk, qed.
--backing-vol-format string is the format of
the snapshot backing volume; raw, bochs, qcow, qcow2, qed, vmdk, host_device.
qed and vmdk format added. verification passed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.