Hide Forgot
Description of problem: When create a new volume in storage, select format as bochs,cloop,dmg,iso in dropdown list, allocate the capacity, Finish. No error message will display, but Found that it actually does not take effect to new this volume. And these volumes will not display in storage pool. Version-Release number of selected component (if applicable): # uname -a Linux dhcp-65-85.nay.redhat.com 2.6.32-99.el6.x86_64 #1 SMP Fri Jan 14 10:46:00 EST 2011 x86_64 x86_64 x86_64 GNU/Linux kernel-2.6.32-99.el6.x86_64 qemu-kvm-0.12.1.2-2.129.el6.x86_64 libvirt-0.8.7-1.el6.x86_64 virt-manager-0.8.6-1.el6 How reproducible: Always Steps to Reproduce: 1.Open virt-manager and Click connection to open Connection details 2.Click Storage tab in Connection details, Select one active pool and create New volume button, Divert to new storage volume page 3.Input the volume name, and select format as bochs/cloop/dmg/iso in dropdown list,allocate the capacity, Finish Actual results: No error message displays, but the storage pool can not find these volumes Expected results: These volumes can be added into storage pool correctly Additional info:
We shouldn't list all those formats in virt-manager, since they have never really been implemented in libvirt, and some can't be created with qemu-img anyways.
Fixed in virt-manager-0.8.6-3.el6
Verfied it on build : virt-manager-0.8.6-3.el6.noarch libvirt-0.8.7-13.el6.x86_64 qemu-kvm-0.12.1.2-2.150.el6.x86_64 kernel-2.6.32-120.el6.x86_64 Steps: 1. Open virt-manager and Click connection to open Connection details; 2. Click the 'Storage' tag; Select one active pool, and click 'New volume'; Divert to new storage volume page; 3. Input the volume name, and select format as raw/cow/qcow/qcow2/vmdk/vpc in dropdown list,allocate the capacity. Finish; 4. These volumes can be added into storage pool correctly. Verification is passed.
Verfied it Pass on build : virt-manager-0.8.6-3.el6.noarch libvirt-0.8.7-17.el6.x86_64 qemu-kvm-0.12.1.2-2.153.el6.x86_64 kernel-2.6.32-130.el6.x86_64
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0637.html