...
A deployment Ansible playbook is available 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)
...
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).
The
vcpupin
element specifies which host's physical CPUs the domain vCPU will be pinned to. Use this value only for performance driven VMs.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 |
If you deploy a machine with real time vcpu scheduler, you must set the |