Bug 1089457 - qcow2 extension forced even when format set to raw
Summary: qcow2 extension forced even when format set to raw
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-19 07:23 UTC by Joseph D. Wagner
Modified: 2014-05-02 20:57 UTC (History)
3 users (show)

Fixed In Version: virt-manager-1.0.1-3.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-02 20:57:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joseph D. Wagner 2014-04-19 07:23:46 UTC
Description of problem:
When creating a new VM, the storage default format is now qcow2 (was raw).  Changing the format to raw, however, does not change the extension on the file.

This can lead to some confusion if the virtual machine is moved, and the admin doesn't realize that it is really a raw image that is just named with a qcow2 extension.

It appears that the wizard is creating the file too early in the process.  It should hold off until Begin Installation is selected.

Version-Release number of selected component (if applicable):
virt-manager-1.0.1-1.fc20.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Create a new VM.
2. Check box to configure advanced options before install.
3. Change image format on storage from qcow2 to raw.
4, Image still has qcow2 extension.

Actual results:
vm machine name: fedora20
with image format changed from default of qcow2 to raw
vm image name: fedora20.qcow2

Expected results:
vm machine name: fedora20
with image format changed from default of qcow2 to raw
vm image name: fedora20.img

Comment 1 Cole Robinson 2014-04-21 21:06:26 UTC
That UI bit isn't doing what you think it's doing. It's only used to tell libvirt what storage format the disk image is already in, it does _not_ transparently reformat the disk to a different format. Libvirt can't do the auto detection since there are security implications.

I've clarified this upstream now:

commit 70da20682c9aba1e2bc738b19dfc6bb714d38496
Author: Cole Robinson <crobinso>
Date:   Mon Apr 21 17:04:33 2014 -0400

    details: Explicit warn that 'format' doesn't change image format (bz 1089457

Comment 2 Fedora Update System 2014-04-29 18:52:26 UTC
virt-manager-1.0.1-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/virt-manager-1.0.1-3.fc20

Comment 3 Fedora Update System 2014-05-01 07:04:00 UTC
Package virt-manager-1.0.1-3.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-1.0.1-3.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-5846/virt-manager-1.0.1-3.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-05-02 20:57:21 UTC
virt-manager-1.0.1-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.