On 01.02.2014 06:43, Marcus wrote:
[root@server ~]# qemu-img create -f qcow2 -o preallocation=metadata
imagepre.qcow2 10G
Formatting 'imagepre.qcow2', fmt=qcow2 size=10737418240 encryption=off
cluster_size=65536 preallocation='metadata'
[root@server ~]# qemu info imagepre.qcow2
-bash: qemu: comm
On 01.02.2014 07:14, Marcus wrote:
Oh yes, and storage overprovisioning doesn't currently work for KVM
storage types, but it's a relatively simple fix:
Let me know when you need someone to ask for a cherry pick. :-)
Qcow files scream overprovisioning.
Lucian
--
Sent from the Delta quadrant us
Oh, thank you for information. I will look into.
2014-02-01 Marcus :
> Oh yes, and storage overprovisioning doesn't currently work for KVM
> storage types, but it's a relatively simple fix:
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-5806
>
> On Sat, Feb 1, 2014 at 12:12 AM, Marcus wrote
Oh yes, and storage overprovisioning doesn't currently work for KVM
storage types, but it's a relatively simple fix:
https://issues.apache.org/jira/browse/CLOUDSTACK-5806
On Sat, Feb 1, 2014 at 12:12 AM, Marcus wrote:
> I don't think you'd have to change anything. Cloudstack (at least for
> acco
I don't think you'd have to change anything. Cloudstack (at least for
accounting purposes) considers all storage 'fat' and calculates
capacity per the disk offering size compared to total size of the
primary pool. Then you can add an overprovisioning factor to fit your
needs in the config options.
Yes, preallocation=metadata creates a large file full of holes. and
maybe I need to modify storage consumption measuring method of
CloudStack to care this kind sparse file.
To satisfy my needs, just turning on preallocation=metadata by default
or making it configurable from agent.properties is eno
Ok, so not technically sparse in the sense that you have a large file
full of holes, but it's still not allocating the entire disk upfront.
You get the same result of disk savings either way, existing
cloudstack installs with qcow2 are still saving space in the same
manner.
On Fri, Jan 31, 2014 at
Here are my tests, using stock centos 6.5 qemu-img:
[root@server ~]# qemu-img create -f qcow2 image.qcow2 10G
Formatting 'image.qcow2', fmt=qcow2 size=10737418240 encryption=off
cluster_size=65536
[root@server ~]# qemu-img info image.qcow2
image: image.qcow2
file format: qcow2
virtual size: 10G (1
Yes, no_option.img is only 256k in size. it's sparse.
On Fri, Jan 31, 2014 at 11:38 PM, Yoshikazu Nojima wrote:
>>I don't think preallocation=metadata is required for sparse qcow2.
>>Just if you want it to NOT be sparse for metadata.
>
> I think it is required. Please see the output below. Only
>
>I don't think preallocation=metadata is required for sparse qcow2.
>Just if you want it to NOT be sparse for metadata.
I think it is required. Please see the output below. Only
"metadata.img" is a sparse file.
==
[root@ut1-qmb-rd5c test]# qemu-img create -f qcow2 -o
preallocation=off
I don't think there needs to be a lot of engineering around this, we
can probably just turn on preallocation=metadata by default.
If there are any other options/features you want to add (such as
preallocation=full), they can simply be turned on via agent.properties
and/or global/hypervisor/cluster
I don't think preallocation=metadata is required for sparse qcow2.
Just if you want it to NOT be sparse for metadata.
I also remember hearing that either recent qemu-img has a decent
preallocation by default now, or that performance has improved such
that it doesn't matter. Will need to do some re
Hello Nux,
Thank you for your comment. I will prepare feature specification.
Regards,
2014-01-31 Nux! :
> On 31.01.2014 20:24, Yoshikazu Nojima wrote:
>>
>> Afternoon All,
>>
>> Is there anyone working on adding volume provisioning method option?
>> As you know, thin provisioning of a volume sav
On 31.01.2014 20:24, Yoshikazu Nojima wrote:
Afternoon All,
Is there anyone working on adding volume provisioning method option?
As you know, thin provisioning of a volume save consumption of a
storage, and fat provisioning improves IOPS performance.
Especially, Qcow2 can save storage consumptio
Afternoon All,
Is there anyone working on adding volume provisioning method option?
As you know, thin provisioning of a volume save consumption of a
storage, and fat provisioning improves IOPS performance.
Especially, Qcow2 can save storage consumption and achive relatively
better performance than
15 matches
Mail list logo
