Bug 511065 - Add a storage volume (file) allocation is not in megabytes as specified.
Summary: Add a storage volume (file) allocation is not in megabytes as specified.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-13 14:27 UTC by Gene Czarcinski
Modified: 2009-07-15 00:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-15 00:28:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gene Czarcinski 2009-07-13 14:27:27 UTC
Description of problem:
The dialog to "add a storage volume" (create a new virtual disk file) has a box where the max capacity can be specified with a default of "1000" and a label of "MB".  What actually gets allocated is 1MB so that the label is incorrect.

What is needed for specifying max capacity should have the ability of specifying the unit (e.g., KB, MB, GB, TB) ... or at least do GB .. KB is silly.

Version-Release number of selected component (if applicable):
F11 + preview

How reproducible:
everytime

Comment 1 Cole Robinson 2009-07-15 00:28:12 UTC
I just tried this, allocating a 'raw' volume, and it definitely created what I asked for. I entered 1000 for allocation and 1000 for capacity, the resulting image:

$ sudo du -h /var/lib/libvirt/images/test.img
1001M	/var/lib/libvirt/images/test.img

So closing this as NOTABUG. Keep in mind, if you are using qcow2, the image is deliberately not fully allocated, it grows on demand (that is one of the benefits of qcow).

Please reopen if you can reproduce.


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