Creating an IP Office KVM virtual machine file

Last Updated : Jul 17, 2025 |

About this task

Use this process to prepare a copy of the downloaded IP Office .qcow2 file for use as an IP Office KVM virtual machine.

Before you begin

Procedure

  1. Login to the KVM CLI as the custadm user.
    1. Run "swversion" to check ASP 130 software version. If the version is 6.0.0.1.0 or greater, move to step 5 (copy file using WinSCP). If not, update the ASP 130 to the latest service pack. If software version is 6.0.0.0.0, update ASP to the latest software. The initial ASP service pack creates the /var/lib/libvirt/staging staging directory with the correct ownership and permissions. The sudo command will not be necessary in the staging directory if version is at 6.0.0.1.0 or greater. If you cannot update your ASP 130 R6.0.0.0.0 to a later release, then perform steps 2 through 4 below.
  2. Enter sudo ls -ld /var/lib/libvirt/staging.

    If you cannot upgrade to 6.0.0.1.0 or greater, perform step 3 and 4.

  3. If the command did not find the directory, create the directory:
    1. Enter the following commands:

      sudo mkdir /var/lib/libvirt/staging

      sudo chown custadm:wheel /var/lib/libvirt/staging

    2. Enter sudo ls -ld /var/lib/libvirt/staging again.
  4. Check the permissions shown are drwxr-x--- 2 custadm wheel ....

    These allow the custadm user to write into the directory using sudo commands. If the permissions shown are different:

    1. Enter sudo chown custadm:wheel /var/lib/libvirt/staging
    2. Run sudo ls -ld /var/lib/libvirt/staging again and check the permissions.
  5. Using an SCP file transfer tool, for example WinSCP, and the custadm user credentials, copy the downloaded IP Office .qcow2 file into the /var/lib/libvirt/staging directory.
  6. Enter cd /var/lib/libvirt/staging.
  7. Enter sudo ls -lh and check for the IP Office .qcow2 file.
  8. The downloaded IP Office .qcow2 file is a thin-provisioned file. You must create a thick-provisioned copy which you can then use as an IP Office KVM virtual machine. Enter:

    • sudo qemu-img convert -O qcow2 -o preallocation=full <thin filename> <thick filename>

    For example:

    • sudo qemu-img convert -O qcow2 -o preallocation=full IpolCPERHELKVM-12_1_0_80-disk.qcow2 ipo_primary.qcow2

  9. Move the thick provisioned .qcow2 file to the virtual machine images directory. Enter:

    • sudo mv -i <thick filename> <destination>

    For example:

    • sudo mv -i ipo_primary.qcow2 /var/lib/libvirt/images

  10. Enter cd /var/lib/libvirt/images.
  11. Enter sudo ls -ltr and check for the thick-provisioned file.
  12. Change the file owner and permission of the thick-provisioned file by entering the following commands:

    • sudo chown qemu:qemu <filename>

    • sudo chmod 640 <filename>

    For example:

    • sudo chown qemu:qemu ipo_primary.qcow2

    • sudo chmod 640 ipo_primary.qcow2

  13. If no longer required, for example to create a file for another IP Office virtual machine, delete the thin-provisioned file from the /var/lib/libvirt/staging folder. Enter:

    • rm /var/lib/libvirt/staging/<thin filename>

    For example:

    • rm /var/lib/libvirt/staging/IpolCPERHELKVM-12_1_0_80-disk.qcow2

Next Steps

Related information
KVM Virtual machine deployment on an Avaya ASP 130 R6