Deploying AE Services on ASP R6.0.x (KVM on RHEL 8.10) using KVM Cockpit

Last Updated : Aug 04, 2026 |
Prolog information
Application Enablement Services requires two network interfaces.
AE Services provides an OVA that contains qcow2 file.
Before you begin
  • Install ASP R6.0.x (KVM on RHEL 8.10).
    For more information, see Installing the Avaya Solutions Platform 130 Series at https://support.avaya.com/css/public/documents/101091802.
  • Download the image from AE Services KVM image from PLDS to your computer.
  • Login to the ASP R6.0.x CLI with custadm credentials.
  • Check if /var/lib/libvirt/staging exists.
    sudo ls -ld /var/lib/libvirt/images
  • Ensure to remove the older images from the staging folder.
    Ensure sufficient space is available in the staging folder to copy the KVM image.
  • If the staging folder does not exist, create it using the following commands:
    sudo mkdir /var/lib/libvirt/staging
    sudo chown custadm:wheel /var/lib/libvirt/staging
  • Verify file permissions. The above chown command allows the custadm write into this directory with sudo. The permissions must appear as seen below:
    drwxr-x---. 2 custadm wheel 6 Oct 23 14:32 /var/lib/libvirt/staging
  • Copy the AE Services KVM image to the ASP R6.0.x host in /var/lib/libvirt/staging using winscp and custadm credentials.
  • If not still in the CLI, login again to the ASP R6.0.x CLI with custadm credentials.
    Note:
    All the following commands MUST be prefaced with “sudo”:
  • Run the following command to verify the AE Services KVM image available in the staging folder: sudo ls -lr /var/lib/libvirt/staging
  • Go to /var/lib/libvirt/staging folder, and run the following command to extract the ova file: sudo tar -xvf AES-10.2.0.0.0.198.20231107-e70-00-kvm.ova
  • KVM OVA file extracts the following files:
  • AES-10.2.0.0.0.198.20231107-e70-00-kvm.cert
    • AES-10.2.0.0.0.198.20231107-e70-00-kvm.mf
    • AES-10.2.0.0.0.198.20231107-e70-00-kvm.ovf
    • AES-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
  • The extracted qcow2 images are in thin provision format. The qcow2 images MUST be converted to thick provision. When running the commands to convert to thick provision, a unique identifier can be added to the new qcow2 image. Avaya recommends to use VM name as a unique identifier. For example:
    AES-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
    To
    AES[Unique Identifier]-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
  • Ensure you are in the /var/lib/libvirt/staging directory before you proceed to convert AES-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2 (thin) to AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2(thick).
    sudo qemu-img convert -O qcow2 -o preallocation=full AES-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2 AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
  • To verify that the conversion is successful and verify the disk size, run the following commands:
    • sudo qemu-img info AES-10.2.0.0.0.198.20231107-e70-00-kvm.qcow
      Disk size must display as 2.97 GiB
    • sudo qemu-img info AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
      Disk size must display as 55 GB
  • Copy the AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2 to the /var/lib/libvirt/images directory. Ensure you are in the /var/lib/libvirt/staging directory before performing these steps:
    • cd /var/lib/libvirt/staging
    • sudo cp AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2 /var/lib/libvirt/images
  • Ensure the images are present in the /var/lib/libvirt/images directory.
    • cd /var/lib/libvirt/images
    • sudo ls -lr
  • From the /var/lib/libvirt/images directory, run the following command to change the owner and permissions to 640 on the files:
    • sudo chown qemu:qemu AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
    • sudo chmod 640 AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2
  • Go to /var/lib/libvirt/staging directory and remove all the extracted images and converted images. This is important to ensure that there is sufficient space for future deployments of KVM images. Do NOT remove files from the “images” directory.
    • cd /var/lib/libvirt/staging
      sudo ls -lr
      sudo rm *AES*
  1. Login to the KVM Cockpit web console as custadm in the following format: https://<IP address or FQDN of KVM host>:9090.
  2. For administration actions, on the top-right of the window, click on the Limited access button.
    ADDITIONAL INFORMATION:
    Note:
    VMs are not visible when in Limited access mode!
  3. In the Switch to administrative access window, enter the password for custadm.
    ADDITIONAL INFORMATION:
    The Limited access button on the top-right of the window changes to Administrative access.
  4. Navigate to SystemVirtual MachinesImport VM.
  5. In the Import a virtual machine window, do the following:
    1. In the Name field, enter a name for the AE Services virtual machine.
    2. In the Disk Image field, select the AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2 image of the Application Enablement Services on the KVM Cockpit host under /var/lib/libvirt/images/ dictionary.
    3. In the Operating System field, select RHEL 8 Unknonwn version.
    4. In the Memory field, select the required memory in MiB format.
      ADDITIONAL INFORMATION:
      Note:
      Based on the required footprint, enter a value in the Memory field.
    5. Click Import and edit.
      ADDITIONAL INFORMATION:
      Virtual Machine details page appears.
    6. Under the Disks section, verify the AESThick-10.2.0.0.0.198.20231107-e70-00-kvm.qcow2 image disk image size is correctly displayed in the Capacity field. By default, virtio is selected under the Bus field, and this needs to be modified.
  6. Under the Disks section, click Edit.
  7. In the Edit <attributes name> window, do the following:
    1. in the Bus field, select scsi.
    2. In the Cache field, select directsync.
    3. click Save.
    ADDITIONAL INFORMATION:
    In the Disks section, ensure that scsi appears under the Bus field and directsync appears under the Additional Cache field.
  8. In the Overview section, in the Firmware field, select UEFI and click Save.
  9. In the Overview section, in the CPU field, click edit.
    ADDITIONAL INFORMATION:
    CPU Details window opens.
  10. In the CPU details window, based on the required footprint, enter a value in the vCPU Maximum and vCPU Count fields.
  11. Select the default host-model mode.
  12. Enter values in the vCPU Maximum and vCPU Count fields, based on the required footprint.
    ADDITIONAL INFORMATION:
  13. Click Apply.
  14. In the Network interfaces section, click Edit and select the Network Bridge, and click Save.
    ADDITIONAL INFORMATION:
    AE Services requires two NICs:
    • NIC1 for Public IP address
    • NIC2 is for Out of Band Management
  15. To add more network interfaces, under the Network interfaces section, click Add network interface and do the following:
    1. In the Interface type field, select Bridge to LAN.
    2. From the Source field, select the required network bridge.
    3. Click Add.
  16. On the virtual machine, click Run to start the AE Services virtual machine.
Next steps
On first boot of tAE Services configure the virtual machine, follow the AE Services deployment guide.