[ovirt-devel] QCOW2 support for base images vs GlusterFS support

[Christopher Pereira]

Hi,

4:23 AM and this paradox is struggling my head...

Can someone please confirm if oVirt supports QCOW2 *base* images?

AFAIK, oVirt only supports QCOW2 for *snapshots* not base images. Base 
images must always be in RAW format and there is no way to create QCOW2 
disks in Engine [1].
On the other hand, working with RAW images on a GlusterFS storage is 
inefficient because of [2]. in fact, sparse-files performance is 
unacceptable [3].

Please confirm, comment or ignore.

[1] : https://bugzilla.redhat.com/show_bug.cgi?id=1282654
[2] : https://bugzilla.redhat.com/show_bug.cgi?id=1220173
[3] : For example.: A empty RAW disk image file with 2 TB virtual-size 
and less then 1 MB physical-size is treated by Gluster as a 2 TB 
physical-size file (TB's of useless zeros traversing the DataCenter's 
LAN during many hours).