Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
Moving to POST:
commit 2872155bfe8e95334116e216f369539d1ec5c7cb
Author: Michal Privoznik <mprivozn>
AuthorDate: Mon Jun 18 13:20:01 2012 +0200
Commit: Michal Privoznik <mprivozn>
CommitDate: Mon Jun 18 14:40:32 2012 +0200
virsh: Update vol-create-as manpage
as we support qed format as well.
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.
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
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: