| Summary: | virt-manager should add "qed" option for storage format type. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Daisy Wu <jwu> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.3 | CC: | gkong, mzhan, rwu, yupzhang, zpeng |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
No documentation needed
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 12:39:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Daisy Wu
2012-02-20 09:08:56 UTC
Fixed upstream: http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=92c2bf6b30babd9d7cf152f8d62f59ac37a1b466 Fixed in virt-manager-0.9.0-11.el6 This bug verified with: virt-manager-0.9.0-11.el6 libvirt-0.9.10-9.el6.x86_64 python-virtinst-0.600.0-8.el6.noarch qemu-kvm-0.12.1.2-2.269.el6.x86_64 Steps: 1. Launch virt-manager, New a guest, then 'Customize configuration before install', click Finish. Divert to guest details page, Click Add Hardware -> Storage ->Storage format-> qed 2. After installation, the guest can start successfully and can discover the qed disk. 3. For a health existing guest, Click Add Hardware -> Storage -> Storage format->qed 4. Guest works well and can discover the qed disk. Changed the status 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 documentation needed
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-2012-0785.html |