Thanks, what about:
<cpu mode='custom' match='exact'> <model fallback='forbid'>SandyBridge</model> <feature policy='disable' name='x2apic'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='pdcm'/> <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='dtes64'/> <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>
that should give you the same (feature-wise) CPU but using SandyBridge rather than Westmere model.
And BTW, it looks like we have a bug since
<cpu mode='custom' match='exact'> <model fallback='forbid'>SandyBridge</model> <feature policy='force' name='x2apic'/> </cpu>
should work even if the host CPU does not support x2apic (and AFAIK x2apic is one of the features that QEMU will emulate) but I tried that and libvirt is complaining that x2apic is not supported by host CPU.
Thanks, what about:
<cpu mode='custom' match='exact'> 'forbid' >SandyBridge< /model>
<model fallback=
<feature policy='disable' name='x2apic'/>
<feature policy='require' name='osxsave'/>
<feature policy='require' name='pdcm'/>
<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='dtes64'/>
<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>
that should give you the same (feature-wise) CPU but using SandyBridge rather
than Westmere model.
And BTW, it looks like we have a bug since
<cpu mode='custom' match='exact'> 'forbid' >SandyBridge< /model>
<model fallback=
<feature policy='force' name='x2apic'/>
</cpu>
should work even if the host CPU does not support x2apic (and AFAIK x2apic is
one of the features that QEMU will emulate) but I tried that and libvirt is
complaining that x2apic is not supported by host CPU.