Overview

This page outlines the requirements for deploying the Continuous Compliance Engine via Linux KVM, as well as recommended configuration parameters.

Contact a Delphix representative to request this capability. Delphix will assist in assuring that all KVM requirements are met to successfully run a Continuous Compliance Engine with the most appropriate configurations for the use case.

If the Delphix Continuous Compliance Engine compete with other virtual machines on the same host for resources, it will result in increased latency for all operations.

With that, it is crucial that your KVM host is not over-subscribed, eliminating the possibility of insufficient resources for the Continuous Compliance Engine. This includes allowing a percentage of CPU resources for the hypervisor itself, as it can de-schedule an entire VM, in a case where the hypervisor is needed for managing I/O or computing resources.

The KVM ecosystem includes many versions/variations. Delphix is announcing general support for KVM, but will forego any formal certification for specific versions, focusing rather on declared support for specific Linux Kernels.

Delphix disk storage capabilities are based on the backend storage provided. Performance, redundancy, and stability characteristics are determined by the hypervisor or Cloud provisioned storage.

Starting from release 2025.5.0.0, newly installed Delphix Continuous Compliance engines support UEFI boot with secure boot disabled. When configuring an engine via CLI or XML file, include the following parameters: --boot loader=/usr/share/OVMF/OVMF_CODE.fd, loader.readonly=yes, loader.type=pflash, loader.secure=no

Pre-requisites

  1. The KVM provider must explicitly state that the Ubuntu 24.04 kernel is supported by their variation of KVM.

    1. Most, if not all, KVM hypervisor providers should have public facing documentation that includes support matrices for guest OS compatibility. If the KVM hypervisor provider does not explicitly state support for Ubuntu kernel version 20.04, Delphix cannot support the KVM provider.

      1. As an example, RedHat Linux (a KVM hypervisor provider), provides a publicly accessible guest operating system support matrix. As of March 2024, this matrix does not include support for any Ubuntu guest OS, and therefore Delphix would also not support deployment on RedHat Linux KVM.

      2. Oracle Linux (a different KVM hypervisor provider) also provides a publicly accessible guest operating system support matrix, which declares support for Ubuntu 24.04. In this case, since the hypervisor provider declares support for the Delphix Ubuntu kernel, Delphix will support deployment on Oracle Linux KVM.

  2. A check of the Delphix appliance on the variation/version of KVM.

    1. It is required that a Delphix representative works with the organization to check the Delphix appliance (and/or use case) on the specified KVM variation/version. This check will ensure that the software is compatible.

Virtual CPUs

Requirements

Notes

8 vCPUs

  • CPU resource shortfalls can occur on an over-committed host or if facing competition for host resources during high I/O utilization.

  • CPU reservations are strongly recommended for the Delphix VM, to guarantee the full complement of CPUs, even when resources are overcommitted.

  • It is suggested to use a single core per socket, unless there are specific requirements for other VMs on the same KVM host.

Never allocate all available physical CPUs to virtual machines.

  • A CPU for the KVM Server to perform hypervisor activities must be set aside before assigning vCPUs to Delphix and other VMs.

  • It is recommended that a minimum of 8-10% of the CPUs available are reserved for hypervisor operation. (e.g. 12 vCPUs on a 128 vCore system).

Memory

Requirements

Notes

128 GB vRAM (recommended)
64GB vRAM (minimum)

  • More memory will provide better performance.

  • Memory reservations are required for the Delphix VM. The performance of the Continuous Compliance Engine will be significantly impacted by the over-commitment of memory resources in the KVM Server. 

  • Reservations ensure that the Continuous Compliance Engine will not be forced to swap pages during times of memory pressure on the host. A swapped page will require more time from orders of magnitude to be brought back to physical memory, from the KVM swap device.

Memory for the KVM Server to perform hypervisor activities must be set aside before assigning memory to Delphix and other VMs. 

  • Failure to ensure sufficient memory for the host can result in a hard memory state for all VMs on the host, which will result in a block for memory allocations.

Network

Requirements

Notes

Virtual ethernet adapter requirements.

  • Jumbo frames are highly recommended to reduce CPU utilization, decrease latency, and increase network throughput (typically 10-20% throughput improvement).

  • A 10GbE NIC/network is recommended for performance dSource and VDB operations.

If the network load in the KVM Server hosting the Continuous Compliance Engine VM is high, dedicate one or more physical NICs to the Continuous Compliance Engine.

  • Adding NICs only works if VMs are discovered using different interfaces. The NFS/iSCSI mounts will only use the network associated with the discovery.

  • See Network connectivity requirements for information about specific port configurations.

SCSI controller

When adding virtual disks, make sure that they are evenly distributing the load across the maximum of four virtual SCSI controllers. Spreading the disks across available SCSI controllers evenly will ensure optimal I/O performance from the disks. For example, a VM with 4 SCSI controllers and 8 virtual disks should distribute the disks across the controllers as follows:

  • disk0 = SCSI(0:0) - System Disk on Controller 0 Port 0

    • (ignore for purposes of load balancing)

  • disk1 = SCSI(0:1) - Data Disk on Controller 0 Port 1

  • disk2 = SCSI(1:1) - Data Disk on Controller 1 Port 1

  • disk3 = SCSI(2:1) - Data Disk on Controller 2 Port 1

  • disk4 = SCSI(3:1) - Data Disk on Controller 3 Port 1

  • disk5 = SCSI(0:2) - Data Disk on Controller 0 Port 2

  • disk6 = SCSI(1:2) - Data Disk on Controller 1 Port 2

  • disk7 = SCSI(2:2) - Data Disk on Controller 2 Port 2

  • disk8 = SCSI(3:2) - Data Disk on Controller 3 Port 2

For load purposes, we generally focus on the Delphix storage (data disks) and ignore the controller placement of the system disk.

General storage 

Using a minimum of four disks to run your Continuous Compliance Engine is recommended. One disk is used for the Delphix File System (DxFS), to ensure that its file systems are always consistent on disk without additional serialization. The other three, or more equally, sized disks will be used for metadata storage. This also enables the Continuous Compliance Engine to achieve higher I/O rates by queueing more I/O operations to its storage.

Requirements

Notes

Storage used for Delphix must be provisioned from storage that provides data protection.

  • For example, using RAID levels with data protection features, or equivalent technology. 

  • The Continuous Compliance Engine does not protect against data loss originating at the hypervisor or SAN layers.

Deploy Delphix OVA on KVM

Most KVM users should deploy the qcow2 image that Delphix publishes directly on the Delphix download site (credentials required). This is the supported and recommended format for KVM environments.

Prerequisites

  • KVM host with virtualization enabled

  • Minimum resources (see Deployment for KVM):

    • 8 vCPU

    • 128 GB RAM

    • System + data disks as described in the KVM deployment guide

  • Network access per customer environment

  • Thick provision the attached virtual disks for Delphix data storage to ensure predictable performance. Underlying physical LUNs may still be thin provisioned, depending on backend storage capabilities.

Procedure using qcow2

  1. Download the qcow2 image from the Delphix Download Site.

  2. Create a new VM in your KVM environment (e.g., virt-manager or virsh).

    1. Assign CPU/memory based on the prerequisites.

    2. Attach the qcow2 image as the boot/system disk.

    3. Add additional virtual disks for Delphix data storage.

  3. Configure networking according to your environment.

  4. Boot the VM and continue with your Initial system configuration.

Last updated
Jan 7, 2026