You want to deploy your application on SEAPATH within a Virtual Machine (VM), you have 2 options:

SEAPATH uses QEMU and Libvirt to deploy virtual machines. With this technology, two elements are needed:

A libvirt XML configuration file: This file describes all the devices needed by the VM. It can be memory, cpu information, interfaces ...
A VM disk image: This file represents the disk of the virtual machine, it will contain the kernel as well as the filesystem. Common format for Linux based VM is qcow2

SEAPATH use Ansible and vm_manager to deploy VM on SEAPATH hypervisor:

A deployment Ansible playbook is available there
- More documentation can be found there
In Ansible inventories you can specify:
- The libvirt XML file used
  - Several libvirt xml templates are provided on SEAPATH. They allow you to configure your VM with different options such as real-time capabilities or non real-time capabilities
  - Detailed documentation can be found there.
- The disk image (qcow2) used, with 2 options
  - Based on generic SEAPATH VM
  - Using your own disk image (ex: Windows, Ubuntu…etc)

Use a generic SEAPATH VM

If you need a virtual machine for testing or for deploying your application, you can use generic SEAPATH VM which contains:

Information on how to build a disk image in detail is available here for a Yocto VM, or here for a Debian VM.

Use your own VM

The supported disk image on SEAPATH is qcow2 used by qemu.

It is possible to convert alternative disk image format to qcow2 thanks to qemu-img. Refer to qemu documentation.