...

• Add VM in the cluster:

  Code Block
  language bash
  vm-mgr create --name NAME --xml /path/to/configuration.xml --image /path/to/disk.qcow2 --disable --force --enable-live-migration --migration-user virtu --migrate-to-timeout 180

  
  

• Check the execution of the resource:

  Code Block
  language bash
  crm status

  
  

• Get the status of the resource:

  Code Block
  language bash
  vm-mgr status --name NAME

  
  

• Delete VM in the cluster:

  Code Block
  language bash
  vm-mgr remove --name NAME

  
  

VM configuration

The official documentation on the XML format of libvirt is here.

Resources

On the XML configuration of a virtual machine, the resource can be specified to know which slice should be used (more details here). So, the virtual machine will only have acces to the CPU associated with the slice.

Possible values:

• /machine/nort
• /machine/rt

Example, for a virtual machine with the real-time:

CPU tunning

In the project, this element will be used to limite the virtual machine (more details here).

• The emulatorpin element specifies which of host physical CPUs the emulator, a subset of a domain not including vCPU or iothreads will be pinned to.
• The vcpupin element specifies which of host's physical CPUs the domain vCPU will be pinned to. It's used to reserved one or more CPUs for a critical virtual machine. So, it's important not use this CPU on another VM.
• The vcpusched element specifies the scheduler type for a particular vCPU. A priority can be setting. In the project, all values greats than 10, it's for the host; equals to 10, it's for the RCU and less than 10, it's to set the priority of the RT vCPU among themselves.

LikeBe the first to like this