Deploying LogLogic EVA on Kernel-Based Virtual Machine

To deploy LogLogic EVA on Linux kernel-based virtual machine (KVM), create a storage pool and a virtual machine. Then connect to the virtual machine via SSH and access LogLogic EVA.

See the characteristics and limitations of LogLogic EVA on KVM.

Prerequisites

Ensure that you meet the following requirements:
  • The <EVA_version>_ova.zip archive, downloaded from the TIBCO eDelivery website. Extract the contents of the archive:
    • TIB_logeva_<version>.asc
    • TIB_logeva_<version>.ova
    • TIB_logeva_<version>.ova.sig
  • A Linux machine having:
    • A supported version of any operating system: CentOS or RHEL. For a complete list of supported platforms and versions, see the LogLogic EVA Readme file.
    • A KVM hypervisor, with the network bridge interface configured

      For more information see https://www.linux-kvm.org/.

    • CPU virtualization enabled

Procedure

  1. Install the virt-v2v using the root user by running the following command:
    [root@localhost ~]# yum install virt-v2v
  2. Create a storage pool by performing the steps at Create a directory-based storage pool in Red Hat documentation.
  3. Convert the .ova file to a KVM-supported format and create a virtual machine by running the following command:
    [root@localhost ~]# virt-v2v -i ova <full_path_to_ova_file> -o libvirt -of qcow2 -os default -n default
    where:
    Parameter Description
    -i ova <full_path_to_ova_file> Specifies the .ova file to be converted
    -o libvirt -of qcow2 Creates a virtual machine in qcow2 file format
    -os default Places the virtual machine in the default pool
    -n default Configures the virtual machine to use the default network
    An example of the output after running the command:
    [root@localhost ~]# virt-v2v -i ova /home/john/Desktop/TIB_logeva_6.3.1.ova -o libvirt -of qcow2 -os default -n default
    [ 0.0] Opening the source -i ova /home/john/Desktop/TIB_logeva_6.3.1.ova
    virt-v2v: warning: making OVA directory public readable to work around
    libvirt bug https://bugzilla.redhat.com/1045069
    [ 4.8] Creating an overlay to protect the source from being modified
    [ 4.8] Initializing the target -o libvirt -os libvirt
    [ 4.9] Opening the overlay
    [ 66.3] Inspecting the overlay
    [ 119.1] Checking for sufficient free disk space in the guest
    [ 119.1] Estimating space required on target for each disk
    [ 119.1] Converting Oracle Linux Server release 7.6 to run on KVM
    virt-v2v: warning: could not add grub2 serial console (ignored)
    virt-v2v: This guest has virtio drivers installed.
    [1931.8] Mapping filesystem data to avoid copying unused and blank areas
    [1942.8] Closing the overlay
    [1944.1] Checking if the guest needs BIOS or UEFI to boot
    [1944.1] Assigning disks to buses
    [1944.1] Copying disk 1/1 to /var/lib/libvirt/lmi-build-6.3.1-sda (qcow2)
    (100.00/100%)
    [2097.2] Creating output metadata
    [2097.3] Finishing off
    The virtual machine is available in Virtual Machine Manager.
  4. From Virtual Machine Manager, change the network to use the bridge that you created:
    1. Select your virtual machine and click Edit > Virtual Machine Details.
    2. Click the bulb icon to view the configuration details of the virtual machine.
    3. In the left pane, select the NIC that is being used for gateway and communication by clicking NIC :xx:xx:xx and set the Network Source field to use the bridge interface that you created.
      If you are using multiple NICs in your LogLogic EVA setup, you must set the Network Source for each NIC.
    4. Click Apply.
  5. Select the storage type as SATA disk.
  6. Click the Power On icon to power on the virtual machine and then click the console icon to open the appliance console.

What to do next