Hide Forgot
Created attachment 473548 [details] virt-manager screen shots Changing, i.e. extending, the size of an already existing virtual hard disk (15 GB) of a KVM image does not seem to be possible. Therefore removing the existing hard disk and creating a new one (50 GB) via the GUI as shown in the attached screen shots. It is recognised that the default path for the hard disk is already existing and whether it should be used or not. After confirming with <yes>, silently the old image size (15 GB) is taken - and the previously entered new image size is silently discarded again. After manually deleting the image in the file system a new virtual hard disk can be created with the desired size. Please adapt the work flow, e.g. by adding an option in the second screen whether the old file should be removed from the file system as well or not. # rpm -qf `which virt-manager` virt-manager-0.8.4-8.el6.noarch
Thanks for the report. I don't want to add a 'delete' option to the disk wizard, we shouldn't be mixing delete operations in with an 'add' dialog. The dialog should be more explicit that you aren't just reusing a 'path' but the actual 'storage', so the wording should be improved.
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. Delete an existed guest(for example, rrr), uncheck 'Delete the associated storage file'; 2. Create a new guest, with the name 'rrr', leave the other steps default; 3. After the step 'Create a disk image on the computer's hard drive', an warning message dialog pop-up, with the message below: 'The following storage already exists, but is not in use by any virtual machine: /var/lib/libvirt/images/rrr.img Would you like to reuse this storage?' 4. Both 'yes' or 'no' are OK for the new guest. Verification is passed.
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