When adding new storage through the wizard or the storage manager in qcow2 format, the resulting image is smaller by a factor of 1000. Example: I request a 10000MB qcow2 image, however I receive a 10MB image. Tested on both x86 && amd64. Reproducible: Always Steps to Reproduce: 1. Go to details on the dropdown for localhost (QEMU) 2. Enter the storage tab 3. Click New Volume 4. Name image, select qcow2 format, and put a max capacity of 10000MB. 5. Create volume and check the size. Actual Results: My created image says 9.77MB... Expected Results: Given me a 9.77GB image. Using kvm-image on the command line works, as does the raw format; other formats may be affected.
What's a few orders of magnitude among friends :) Please post your 'emerge --info' output and then we'll see what the maintainers have to say about this.
I think we can assign this one without emerge --info.
Please try with virt-manager 0.8.2 and reopen if it's still a problem.
This is normal behaviour - http://people.gnome.org/~markmc/qcow-image-format.html The QCOW image format is one of the disk image formats supported by the QEMU processor emulator. It is a representation of a fixed size block device in a file. Benefits it offers over using raw dump representation include: Smaller file size, even on filesystems which don't support holes (i.e. sparse files)
