Deploying WebLM using KVM Cockpit

Last Updated : Nov 26, 2024 |

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 WebLM virtual machine.
    2. In the Disk Image field, select the WebLM-10.1.2.0.0-39690-KVM-4E-THICKdisk1.qcow2 image of the Communication Manager on the KVM Cockpit host under /var/lib/libvirt/images/ directory.
    3. In the Operating System field, select RHEL 8.6 (Oopta) 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 Upgrading standalone Avaya WebLM.

    5. Click Import and edit.

      Virtual Machine details page appears.

      Under the Disks section, verify the WebLM-10.1.2.0.0-39690-KVM-4E-THICKdisk1.qcow2 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.
  11. In the Mode field, keep the default host-model.
  12. Click Apply.
  13. In the Network interfaces section, click Edit and select the Network Bridge, and click Save.
  14. On the virtual machine, click Run to start the System Manager virtual machine.

Next Steps

On first boot of the System Manager virtual machine, log in to the virtual console using the craft/craft01 and provide the configuration and networking parameters.