Bug 511065 - Add a storage volume (file) allocation is not in megabytes as specified.
Add a storage volume (file) allocation is not in megabytes as specified.
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Berrange
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-07-13 10:27 EDT by Gene Czarcinski
Modified: 2009-07-14 20:28 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 20:28:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2009-07-13 10:27:27 EDT
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:
Comment 1 Cole Robinson 2009-07-14 20:28:12 EDT
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.