...
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)
...
It is possible to convert alternative disk image format to qcow2 thanks to qemu-img. Refer to qemu documentation.
Virtual machine and slices
If you configured SEAPATH with machine-rt and machine-nort slices (see Scheduling and priorities), you must put the VM into it. This is done using libvirt resources. The VM will then only have access to the CPU associated with the slice.
Possible values:
/machine/nort/machine/rt
Example, for a virtual machine with the real-time:
|
CPU tuning
In the project, this element will be used to limit the virtual machine (more details here).
...
Use
...
The vcpusched element specifies the scheduler type for a particular vCPU. Use this value only for performance driven VMs.
...
The emulatorpin element specifies which of host physical CPUs the emulator will be pinned to. The emulator describes the management processes of the VM (watchdog, creation, timers, modification). This value is not useful, most of the time.
If you configured CPU restriction for slices (see Scheduling and priorities), all the CPU ranges that you provide for |
...
a supported provider VM
Some provider VM are supported in SEAPATH, you can deploy them following their documentation: