Bug 739487
Summary: | RFE: support qed format on volume creation | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nan Zhang <nzhang> |
Component: | python-virtinst | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | bgollahe, dyuan, hjiang, mzhan, rwu, syeghiay, zpeng |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
No description necessary
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 16:17:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 748554 |
Description
Nan Zhang
2011-09-19 08:52:43 UTC
We actually store this list in virtinst, so that's where the fix is: http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=9b38d38851c1b24783ad94655d8cd19cfeb1f011 Fixed in python-virtinst-0.600.0-4.el6 Verified with kernel-2.6.32-197.el6.x86_64 qemu-kvm-0.12.1.2-2.192.el6.x86_64 libvirt-0.9.4-17.el6.x86_64 python-virtinst-0.600.0-5.el6.noarch virt-manager-0.9.0-7.el6.x86_64 step: 1. Start up virt-manager 2. Edit -> Connection Details -> Storage -> New Volume qed option is in [Format] list for volume creation. 3. Add a qed format volume to the storage. qed format could be created ,displayed and deleted normally. So move the status of this bug to verified. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary 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/RHBA-2011-1643.html |