mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-10-04 21:35:45 +00:00
98b7c37d37
Guest CPU definitions with mode='custom' and missing <vendor> are expected to run on a host CPU from any vendor as long as the required CPU model can be used as a guest CPU on the host. But even though no CPU vendor was explicitly requested we would sometimes force it due to a bug in virCPUUpdate and virCPUTranslate. The bug would effectively forbid cross vendor migrations even if they were previously working just fine. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
18 lines
678 B
XML
18 lines
678 B
XML
<cpu mode='custom' match='exact'>
|
|
<model fallback='allow'>Nehalem</model>
|
|
<topology sockets='2' cores='4' threads='1'/>
|
|
<feature policy='force' name='pbe'/>
|
|
<feature policy='force' name='monitor'/>
|
|
<feature policy='require' name='xtpr'/>
|
|
<feature policy='require' name='dca'/>
|
|
<feature policy='force' name='3dnowext'/>
|
|
<feature policy='force' name='svm'/>
|
|
<feature policy='disable' name='sse'/>
|
|
<feature policy='disable' name='sse4.2'/>
|
|
<feature policy='forbid' name='popcnt'/>
|
|
<feature policy='disable' name='3dnow'/>
|
|
<feature policy='require' name='ssse3'/>
|
|
<feature policy='disable' name='vmx'/>
|
|
<feature policy='disable' name='ds_cpl'/>
|
|
</cpu>
|