libvirt/tests/cputestdata/x86_64-host+host-model-nofallback.xml

<cpu mode='custom' match='exact'>
  <model fallback='forbid'>Penryn</model>
  <vendor>Intel</vendor>
  <topology sockets='1' dies='1' cores='2' threads='1'/>
  <feature policy='require' name='dca'/>
  <feature policy='require' name='xtpr'/>
  <feature policy='require' name='tm2'/>
  <feature policy='require' name='est'/>
  <feature policy='require' name='vmx'/>
  <feature policy='require' name='ds_cpl'/>
  <feature policy='require' name='monitor'/>
  <feature policy='require' name='pbe'/>
  <feature policy='require' name='tm'/>
  <feature policy='require' name='ht'/>
  <feature policy='require' name='ss'/>
  <feature policy='require' name='acpi'/>
  <feature policy='require' name='ds'/>
  <feature policy='require' name='vme'/>
</cpu>
cpu: Rework cpuUpdate The reworked API is now called virCPUUpdate and it should change the provided CPU definition into a one which can be consumed by the QEMU command line builder: - host-passthrough remains unchanged - host-model is turned into custom CPU with a model and features copied from host - custom CPU with minimum match is converted similarly to host-model - optional features are updated according to host's CPU Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2016-06-23 16:27:07 +03:00			`<cpu mode='custom' match='exact'>`
cpu: Update guest CPU in host-* mode VIR_DOMAIN_XML_UPDATE_CPU flag for virDomainGetXMLDesc may be used to get updated custom mode guest CPU definition in case it depends on host CPU. This patch implements the same behavior for host-model and host-passthrough CPU modes. 2011-12-19 18:41:16 +04:00			`<model fallback='forbid'>Penryn</model>`
			`<vendor>Intel</vendor>`
conf: add support for specifying CPU "dies" parameter Recently CPU hardware vendors have started to support a new structure inside the CPU package topology known as a "die". Thus the hierarchy is now: sockets > dies > cores > threads This adds support for "dies" in the XML parser, with the value defaulting to 1 if not specified for backwards compatibility. For example a system with 64 logical CPUs might report <topology sockets="4" dies="2" cores="4" threads="2"/> Reviewed-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2019-12-16 14:16:51 +03:00			`<topology sockets='1' dies='1' cores='2' threads='1'/>`
cpu: Update guest CPU in host-* mode VIR_DOMAIN_XML_UPDATE_CPU flag for virDomainGetXMLDesc may be used to get updated custom mode guest CPU definition in case it depends on host CPU. This patch implements the same behavior for host-model and host-passthrough CPU modes. 2011-12-19 18:41:16 +04:00			`<feature policy='require' name='dca'/>`
			`<feature policy='require' name='xtpr'/>`
			`<feature policy='require' name='tm2'/>`
			`<feature policy='require' name='est'/>`
			`<feature policy='require' name='vmx'/>`
			`<feature policy='require' name='ds_cpl'/>`
			`<feature policy='require' name='monitor'/>`
			`<feature policy='require' name='pbe'/>`
			`<feature policy='require' name='tm'/>`
			`<feature policy='require' name='ht'/>`
			`<feature policy='require' name='ss'/>`
			`<feature policy='require' name='acpi'/>`
			`<feature policy='require' name='ds'/>`
			`<feature policy='require' name='vme'/>`
			`</cpu>`