[libvirt] [PATCH v2 1/2] XML schema for CPU flags

Dor Laor dlaor at redhat.com
Sun Nov 8 13:22:37 UTC 2009


On 11/05/2009 05:04 PM, Jiri Denemark wrote:
> Firstly, CPU topology and model with optional features have to be
> advertised in host capabilities:
>
>      <host>
>          <cpu>
>              <arch>ARCHITECTURE</arch>
>              <features>
>                  <!-- old-style features are here -->
>              </features>
>              <model>NAME</model>
>              <topology sockets="S" cores="C" threads="T"/>
>              <feature name="NAME"/>
>          </cpu>
>          ...
>      </host>
>
> Secondly, drivers which support detailed CPU specification have to advertise
> it in guest capabilities:
>
>      <guest>
>          ...
>          <features>
>              <cpuselection/>
>          </features>
>      </guest>
>
> And finally, CPU may be configured in domain XML configuration:
>
> <domain>
>      ...
>      <cpu match="MATCH">
>          <model>NAME</model>

Note that for qemu/kvm we plan of using the model only. The features 
(flags) below will be a function of the model used.
Model is one of core2duo/Nehalem/Merom/...

>          <topology sockets="S" cores="C" threads="T"/>
>          <feature policy="POLICY" name="NAME"/>
>      </cpu>
> </domain>




More information about the libvir-list mailing list