Please note the fact that SPARSE works in conjuctions with QCOW2_OPTIONS="-o preallocation=falloc" OR ..full for QCOW2 images, but NOT neccesarly for RAW, alltough RAW should use the same preallocation options as described in the qemu-img manual. QCOW2_OPTIONS is allso ignored when using TM_MAD=ssh
To Reproduce
Create a cluster with 1 datastore.
Add the SPARSE=no in the DS (ignored)
Add the QCOW2_OPTIONS="-o preallocation=falloc" or "...full" in /etc/one/tmrc (ignored)
Create a new image format = RAW | QCOW2
Create a new VM using the RAW image.
Create a new VM using the QCOW2 image.
Expected behavior
The preallocated space should be taken into account on the hypervisor.
Can be tested with df -h or via the monitoring GUI.
Actual behavior
The deployed VM does not take into account the defined parameters.
Description Hello,
This bug is present on both OpenNebula 6.4.0.1 and OpenNebula 6.8.0, probably all version in between.
The
SPARSE=no
parameter is ignored due to the fact that is not taken into account on:This happens for both RAW and QCOW2 images.
Please note the fact that SPARSE works in conjuctions with
QCOW2_OPTIONS="-o preallocation=falloc"
OR..full
for QCOW2 images, but NOT neccesarly for RAW, alltough RAW should use the same preallocation options as described in the qemu-img manual.QCOW2_OPTIONS
is allso ignored when usingTM_MAD=ssh
Docs: https://docs.opennebula.io/6.8/open_cluster_deployment/storage_setup/local_ds.html?highlight=sparse#additional-configuration
To Reproduce Create a cluster with 1 datastore. Add the SPARSE=no in the DS (ignored) Add the QCOW2_OPTIONS="-o preallocation=falloc" or "...full" in
/etc/one/tmrc
(ignored) Create a new image format = RAW | QCOW2 Create a new VM using the RAW image. Create a new VM using the QCOW2 image.Expected behavior The preallocated space should be taken into account on the hypervisor.
Can be tested with
df -h
or via the monitoring GUI.Actual behavior
The deployed VM does not take into account the defined parameters.