Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 830057 - man doc of vol-create-as format is lack of qed and vmdk
man doc of vol-create-as format is lack of qed and vmdk
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
6.3
x86_64 Linux
medium Severity medium
: rc
: ---
Assigned To: Michal Privoznik
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-08 02:01 EDT by zhpeng
Modified: 2013-09-08 20:03 EDT (History)
9 users (show)

See Also:
Fixed In Version: libvirt-0.9.13-3.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-21 02:16:46 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0276 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2013-02-20 16:18:26 EST

  None (edit)
Description zhpeng 2012-06-08 02:01:38 EDT
Description of problem:
vol-create-as format is lack of qed

Version-Release number of selected component (if applicable):
libvirt-0.9.10-21.el6.x86_64

How reproducible:
100%

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
       string]
           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


Actual results:
vol-create-as format is lack of qed and vmdk

Expected results:
Add qed and vmdk

Additional info:
Comment 2 Michal Privoznik 2012-06-18 07:30:22 EDT
Patch proposed upstream:

https://www.redhat.com/archives/libvir-list/2012-June/msg00718.html
Comment 3 Michal Privoznik 2012-06-18 09:24:43 EDT
Moving to POST:

commit 2872155bfe8e95334116e216f369539d1ec5c7cb
Author:     Michal Privoznik <mprivozn@redhat.com>
AuthorDate: Mon Jun 18 13:20:01 2012 +0200
Commit:     Michal Privoznik <mprivozn@redhat.com>
CommitDate: Mon Jun 18 14:40:32 2012 +0200

    virsh: Update vol-create-as manpage
    
    as we support qed format as well.
Comment 6 zhe peng 2012-07-23 22:46:05 EDT
verify with:
libvirt-0.9.13-3.el6.x86_64

step:
1: #man virsh
.......-
-format string
           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.
Comment 7 errata-xmlrpc 2013-02-21 02:16:46 EST
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.

http://rhn.redhat.com/errata/RHSA-2013-0276.html

Note You need to log in before you can comment on or make changes to this bug.