Converting the qcow2 image to thick-provisioned

Last Updated : Dec 15, 2025 |

About this task

Convert the thin-provisioned qcow2 image downloaded from PLDS to a thick-provisioned format with a unique name for deployment.

Before you begin

  • Ensure you are in the /var/lib/libvirt/staging directory.

  • Before converting files, determine the naming conventions for the thick-provisioned qcow2 images to deploy multiple VMs from the same qcow2 image. Each image must have a unique name. For recommended naming examples, see Supported footprints of Avaya SBC server on Avaya Solutions Platform 130 Appliance R6.0.x.

    For example, when converting to a thick-provisioned qcow2 image, you must label it as EMS or SBC:

    Labeling EMS and SBC

    In this example, one image is labeled as EMS and the other as the first SBC. For subsequent EMS or SBC images, replace the number "1" with the following sequential number.

  • Ensure that you convert the thin-provisioned qcow2 image downloaded from PLDS to a thick-provisioned format.

  • Ensure that the thick image includes a -thick identifier and role label (for example, EMS or SBC) when running the commands.

Procedure

  1. Run the conversion command to create the thick-provisioned image using the thick-provisioned image name.

    For example, run the following command:

    sudo qemu-img convert -O qcow2 -o preallocation=full sbce-10.2.1.0-101-24795.qcow2 sbce-10.2.1.0-101-24795-EMS1-thick.qcow2
  2. Verify both the thin and thick qcow2 files are present in the staging directory.

    For example, run the following command:

    ls -l

    The thin and thick-provisioned image files are listed as follows:

    -rw-r-----. 1 custadm custadm 3417178112 Nov 25 2024 sbce-10.2.1.0-101-24795.qcow2

    -rw-r-----. 1 root root 68730224640 Oct 3 19:54 sbce-10.2.1.0-101-24795-EMS1-thick.qcow2

  3. Check the disk size of the thick image to confirm the conversion was successful.

    For example, run the following command:

    qemu-img info sbce-10.2.1.0-101-24795-EMS1-thick.qcow2

    The disk size shows as 64 GiB for EMS or SBC VMs.

    Note:

    Check the disk size, not the virtual size. In a thin-provisioned qcow2 image, the virtual size also displays as 64 GiB, but the disk size is approximately 3.18 GiB.

    A sample output from the qemu-img info sbce-10.2.1.0-101-24795-EMS1-thick.qcow2 is as follows:

    [custadm@aasp130clv staging]$ qemu-img info sbce-10.2.1.0-101-24795-EMS1-thick.qcow2

    image: sbce-10.2.1.0-101-24795-EMS1-thick.qcow2

    file format: qcow2

    virtual size: 64 GiB (68719476736 bytes)

    disk size: 64 GiB

    cluster_size: 65536

    Format specific information:

    compat: 1.1

    compression type: zlib

    lazy refcounts: false

    refcount bits: 16

    corrupt: false

    extended l2: false

    [custadm@aasp130clv staging]$

  4. Move the thick image to the /var/lib/libvirt/images directory:

    For example, run the following command:

    sudo mv sbce-10.2.1.0-101-24795-EMS1-thick.qcow2 /var/lib/libvirt/images

    You must enter the custadm password before proceeding.

  5. Verify that the image is present in the new directory.

    For example, run the following command:

    cd /var/lib/libvirt/images
sudo ls -l
  6. Change the owner and permissions of the thick image to 640.

    For example, run the following command:

    sudo chown qemu:qemu sbce-10.2.1.0-101-24795-EMS1-thick.qcow2
sudo chmod 640 sbce-10.2.1.0-101-24795-EMS1-thick.qcow2
  7. Confirm the changes.

    For example, run the following command:

    sudo ls -l
  8. Clean up the staging directory to free space for future deployments.

    For example, run the following command:

    cd /var/lib/libvirt/staging
sudo rm *.qcow2
    Note:

    Do not remove any files from the image directory. The cleanup must be completed before deploying additional VMs.