Hide Forgot
Description of problem: virt-manager should add "qed" option for storage format type. Version-Release number of selected component (if applicable): virt-manager-0.9.0-10.el6 libvirt-0.9.10-1.el6.x86_64 python-virtinst-0.600.0-7.el6.noarch qemu-kvm-0.12.1.2-2.230.el6.x86_64 # uname -a Linux localhost.localdomain 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux How reproducible: always Steps to Reproduce: 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 2. For a health existing guest, Click Add Hardware -> Storage -> Storage format Actual results: There are only two types support -> raw and qcow2. Expected results: There should be three types support -> raw, qcow2, qed. Additional info:
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