[libvirt] [PATCH v2 2/6] cpu: Optionally forbid fallback CPU models
Eric Blake
eblake at redhat.com
Mon Jan 16 20:18:05 UTC 2012
On 01/12/2012 04:02 AM, Jiri Denemark wrote:
> In case a hypervisor doesn't support the exact CPU model requested by a
> domain XML, we automatically fallback to a closest CPU model the
> hypervisor supports (and make sure we add/remove any additional features
> if needed). This patch adds 'fallback' attribute to model element, which
> can be used to disable this automatic fallback.
> ---
> Notes:
> Version 2:
> - grammar
>
> +++ b/docs/formatdomain.html.in
> @@ -559,7 +559,7 @@
> <pre>
> ...
> <cpu match='exact'>
> - <model>core2duo</model>
> + <model fallback='allow'>core2duo</model>
> <vendor>Intel</vendor>
> <topology sockets='1' cores='2' threads='1'/>
> <feature policy='disable' name='lahf_lm'/>
> @@ -609,7 +609,15 @@
> <dd>The content of the <code>model</code> element specifies CPU model
> requested by the guest. The list of available CPU models and their
> definition can be found in <code>cpu_map.xml</code> file installed
> - in libvirt's data directory.</dd>
> + in libvirt's data directory. If a hypervisor is not able to use the
> + exact CPU model, libvirt automatically falls back to a closest model
> + supported by the hypervisor while maintaining the list of CPU
> + features. <span class="since">Since 0.9.10</span>, an optional
> + <code>fallback</code> attribute can be used to forbid this behavior,
> + in which case an attempt to start a domain requesting unsupported
s/unsupported/an &/
> + CPU model will fail. Supported values for <code>fallback</code>
> + attribute are: <code>allow</code> (this is the default), and
> + <code>forbid</code>.</dd>
ACK with that nit fixed.
--
Eric Blake eblake at redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 620 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20120116/1a72d5cf/attachment-0001.sig>
More information about the libvir-list
mailing list