Bug 218996 - virt-manager needs to create non-sparse files
Summary: virt-manager needs to create non-sparse files
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Hugh Brock
QA Contact:
Depends On: 217764
TreeView+ depends on / blocked
Reported: 2006-12-08 23:04 UTC by Stephen Tweedie
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version: RC
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2007-02-08 01:35:36 UTC

Attachments (Terms of Use)

Comment 2 Daniel Berrangé 2006-12-08 23:12:44 UTC
I don't think its practical to make it the default behaviour, because we've not
got the infrastructure neccessary to give the user feedback while creating the
file - creating non-sparse files can take a very long time.   

So, either we need to create a general virt-manager preference to allow
non-sparse files to be turned on, or perhaps more usefully, in the new VM
wizard, add a checkbox option to request a non-sparse VM. The latter is similar
to what VMWare provides when creating a guest.

Comment 3 RHEL Product and Program Management 2006-12-08 23:30:33 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 6 Hugh Brock 2006-12-18 21:07:48 UTC
Fixed at virt-manager-0_2_6-5_el5. We create non-sparse files by default with a
checkbox as described above. Also updated the progress dialog to display a
verbose warning when creating a vm with a non-sparse file.

Comment 8 RHEL Product and Program Management 2007-02-08 01:35:36 UTC
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.

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