hypervisor-cpu-baseline

Derives a baseline CPU model with features that are a subset of all CPU descriptions in a specified XML file.

Syntax

Where:

<XML_file>

Specifies a file that describes the CPU capabilities of one or more KVM hypervisors.

Descriptions must adhere to the syntax of the <cpu> element of a domain configuration-XML. To obtain a valid CPU description for a particular KVM hypervisor, issue the domcapabilities command on that hypervisor.

Concatenate the output of the domcapabilities command from all KVM hypervisors for which you want to find a baseline CPU model. Optionally, you can reduce the information for each hypervisor to the CPU snippet.

Selected options

<path_to_emulator>: Specifies the path to the emulator, for example, /usr/bin/qemu-system-s390x.
Omit this specification to make libvirt automatically use the correct path to the currently used emulator. Specify a value only if you are an expert user and need to experiment with a specific path.
<hypervisor_machine_type>: Specifies the hypervisor machine type, for example, s390-ccw-virtio-5.0.
Reduce the supported CPU features to an earlier hypervisor version by specifying the machine type of this version rather than the current hypervisor version. The current version is the default.
--features: Print a verbose description that explicitly specifies all features of the baseline CPU. Omitting this option prints features only if they divert from the CPU model.
--migratable: Omits features that might block migration. For example, a z14 baseline CPU might be reduced to z14-base to mitigate QEMU dependencies.

Usage

Establishing a baseline CPU model

Example

# virsh hypervisor-cpu-baseline cpu.xml
<cpu>
    <model>z13-base</model> 
    <feature policy=’require’ name=’aen’/>
    <feature policy=’require’ name=’aefsi’/>
    <feature policy=’require’ name=’msa5’/>
    ...
    <feature policy=’require’ name=’cmm’/>
</cpu>