libvirt/tests/cputestdata/x86-host+penryn-force-result.xml

<cpu mode='custom' match='exact'>
  <arch>x86_64</arch>
  <model fallback='allow'>Penryn</model>
  <feature policy='require' name='sse4.2'/>
  <feature policy='require' name='popcnt'/>
</cpu>
Add support for cpu mode attribute The mode can be either of "custom" (default), "host-model", "host-passthrough". The semantics of each mode is described in the following examples: - guest CPU is a default model with specified topology: <cpu> <topology sockets='1' cores='2' threads='1'/> </cpu> - guest CPU matches selected model: <cpu mode='custom' match='exact'> <model>core2duo</model> </cpu> - guest CPU should be a copy of host CPU as advertised by capabilities XML (this is a short cut for manually copying host CPU specification from capabilities to domain XML): <cpu mode='host-model'/> In case a hypervisor does not support the exact host model, libvirt automatically falls back to a closest supported CPU model and removes/adds features to match host. This behavior can be disabled by <cpu mode='host-model'> <model fallback='forbid'/> </cpu> - the same as previous returned by virDomainGetXMLDesc with VIR_DOMAIN_XML_UPDATE_CPU flag: <cpu mode='host-model' match='exact'> <model fallback='allow'>Penryn</model> --+ <vendor>Intel</vendor> \| <topology sockets='2' cores='4' threads='1'/> + copied from <feature policy='require' name='dca'/> \| capabilities XML <feature policy='require' name='xtpr'/> \| ... --+ </cpu> - guest CPU should be exactly the same as host CPU even in the aspects libvirt doesn't model (such domain cannot be migrated unless both hosts contain exactly the same CPUs): <cpu mode='host-passthrough'/> - the same as previous returned by virDomainGetXMLDesc with VIR_DOMAIN_XML_UPDATE_CPU flag: <cpu mode='host-passthrough' match='minimal'> <model>Penryn</model> --+ copied from caps <vendor>Intel</vendor> \| XML but doesn't <topology sockets='2' cores='4' threads='1'/> \| describe all <feature policy='require' name='dca'/> \| aspects of the <feature policy='require' name='xtpr'/> \| actual guest CPU ... --+ </cpu> 2011-08-18 10:14:36 +00:00			`<cpu mode='custom' match='exact'>`
tests: Add unit tests for internal CPU APIs 2010-10-07 14:35:17 +00:00			`<arch>x86_64</arch>`
cpu_x86: Use signature in CPU detection code Our current detection code uses just the number of CPU features which need to be added/removed from the CPU model to fully describe the CPUID data. The smallest number wins. But this may sometimes generate wrong results as one can see from the fixed test cases. This patch modifies the algorithm to prefer the CPU model with matching signature even if this model results in a longer list of additional features. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2015-06-25 13:06:19 +00:00			`<model fallback='allow'>Penryn</model>`
			`<feature policy='require' name='sse4.2'/>`
			`<feature policy='require' name='popcnt'/>`
tests: Add unit tests for internal CPU APIs 2010-10-07 14:35:17 +00:00			`</cpu>`