Deploying Session Manager on ASP R6.0.x (KVM on RHEL 8.10) using KVM Cockpit

Last Updated : Jun 10, 2026 |

About this task

Session Manager requires two network interfaces.

Session Manager provides OVA that contains SM.qcow2 file.

Note:

Solution Deployment Manager and Solution Deployment Manager Client does not support KVM on RHEL 8.10 images for a virtualized environment.

Before you begin

Always follow A1SC output for deployment of applications on the host(s). There should never be more than one instance of a specific application on the same host.

Deployment of applications MUST be performed one at a time and artifacts cleaned up/removed prior to deploying then next application.

  • 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 SM KVM image from PLDS to your computer.

  • Login to the ASP R6.0.x CLI with custadm credentials.

  • Run the command sudo ls -ld /var/lib/libvirt/images to check to see the staging folder /var/lib/libvirt/staging.

    Verify if there is sufficient space in the staging folder to copy the KVM image. Ensure to remove the older images from the staging folder.

    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 sudo chown custadm:wheel /var/lib/libvirt/staging command allows the custadm to write into this directory with sudo. The permissions appear as seen below:

    drwxr-x---. 2 custadm wheel 6 Oct 23 14:32 /var/lib/libvirt/staging

  • Copy the Session Manager 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.

Important:

Preface the following commands with sudo.

  • Run the following command to verify the Session Manager 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 SM-x.x.x.x.x-kvm-0x.ova

    KVM OVA file extracts the following files:

    • SM.ovf

    • SM.mf

    • SM.qcow2

SM has different profiles but one image. The disk size may need to be resized based on the SM profile that will be deployed:

  • P1 & P2 will have the same disk size 100GB not required to resize

  • P3 & P4 requires 135 GB, required to resize the disk from 100GB to 135 GB with following command sudo qemu-img resize SM.qcow2 +35G

  • P5 & P6 requires 210 GB, required to resize the disk from 100GB to 210 GB with following command sudo qemu-img resize SM.qcow2 +110G

    The extracted qcow2 images are in thin provision format. The qcow2 images MUST be converted to thick provision. Ensure you are in the /var/lib/libvirt/staging directory before the next steps. 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:

    SMx.x[unique identifier]-system.qcow2

    The examples in this document will simply use the following:

    SMx.x-system.qcow2

  • Convert SM.qcow2 (thin) to SMx.x-system.qcow2 (thick)

    sudo qemu-img convert -O qcow2 -o preallocation=full SM.qcow2

    SMx.x-system.qcow2

To verify that the conversion is successful and to verify the disk size, run the command sudo qemu-img info SMx.x-system.qcow2.

Disk size is displayed based on the profile.

  • P1, P2 = 100GB

  • P3, P4 = 135GB

  • P5, P6 = 210GB

Copy the SMx.x-system.qcow2, to the /var/lib/libvirt/images directory. Ensure you are in the /var/lib/libvirt/staging directory before performing these steps.

  • sudo cp SMx.x-system.qcow2 /var/lib/libvirt/images

  • Verify the images are present in the /var/lib/libvirt/images directory

  • cd /var/lib/libvirt/images

  • sudo ls -lrt

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 SMx.x-system.qcow2

  • sudo chmod 640 SMx.x-system.qcow2

Go to /var/lib/libvirt/staging directory and remove all the extracted images and converted images from the staging directory 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 *SM*

Procedure

  1. Log in 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.
    Figure : 1. Limited access button




    Note:

    You require administrator access in order to view virtual machines. Administrator access is like root access. Ensure that you take care making updates.

  3. In the Switch to administrative access window, enter the password for custadm.
    Figure : 2. Switch to administrative access




    The Limited access button on the top-right of the window changes to Administrative access.

    Figure : 3. Administrative access button




  4. Navigate to System > Virtual Machines > Import VM.
  5. In the Import a virtual machine window, do the following:
    1. In the Name field, enter a name for the Session Manager virtual machine.
    2. In the Disk Image field, select the SMx.x- system.qcow2 image of the Session Manager on the KVM Cockpit host under /var/lib/libvirt/images/ directory.
    3. In the Operating System field, select RHEL 8 version.
    4. In the Memory field, select the required memory in MiB format.
      Note:

      Based on the required footprint, enter a value in the Memory field.

      For more information on footprints, see Supported footprints of Session Manager on ASP R6.0.x (KVM on RHEL 8.10)

    5. Click Import and edit.

      Virtual Machine details page appears.

      Under the Disks section, verify the SMx.x.x- system.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.

      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.

    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.

    For more information on footprints, see Supported footprints of Session Manager on ASP R6.0.x (KVM on RHEL 8.10).

  11. Select the default host-model mode.
  12. Click Apply.
  13. In the Network interfaces section, click Edit and select the Network Bridge, and click Save.
    Session Manager requires two NICs

    • NIC1 is for the Management IP

    • NIC2 is for the Asset IP

  14. 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.
  15. On the virtual machine, click Run to start the Session Manager virtual machine.

Next Steps

On first boot of the Session Manager configure the virtual machine, network properties and follow the Session Manager deployment guide.