Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Adjust qcow2 image files to where 10GB really equals 10GB. #595
Don't know if it is supported or not but I download the qcow2 images for memcached & redis and import them into Openstack. They show to be <100MB on the dashboard however attempting to launch an instance on a 10GB flavor fails to due to the hard-drive being too small.
View the details of the qcow file to see:
10842275840 bytes actually equals 10.8423GB which if I adjust my flavors to be 11GB I am able to launch the instance but then I don't have consistency with the rest of my flavors.
I also don't see why if the qcow2 files is only 30M that why the virtual size needs to be 10GB.
On Sat, Feb 21, 2015 at 1:48 AM, Cory Claflin firstname.lastname@example.org
But why is our 10GB bigger than 10GB?
First of all, our code in build.mk work in powers of 2, not powers of 10,
This almost explains the size you're seeing, except for about 100MB. That
I don't know why this "+" appears here (and I already noted that in a
I believe that to get exactly 10,000,000,000 bytes, you can modify the
Of course, without any changes you can also use fs_size_mb=9000, and it
Fixed on my makefile rewrite branch (see issue #571), removing the superfluous "+" as described above.
On that branch, we now get:
(note how 1024_1024_1024=1073741824, exactly).
Also added an option to set the size in bytes exactly. However, this number is rounded down to the nearest multiple of 512:
(Note 99999744 is 100000000 rounded down to the nearest multiple of 512)
Thanks.....I think...lol If what you did makes the file size smaller then I'll give it another try when the next qcow2 file gets released.
Not meaning to sound lazy and realize that this probably isn't the intended use of the project but I'm not wanting to have to build/compile anything. I would like to be able to just download the qcow2 files for memcache & redis, import them into OpenStack, and have ready to go instances that work with my existing 10GB flavors. If not doable, then thanks for replying and I'll keep building them by hand.