libvirt users - Sep 2019 - Live-Migration not possible: error: operation failed: guest CPU doesn't match specification

Hi,

i have atwo node HA-cluster with pacemaker, corosync, libvirt and KVM.
Recently i configured a new VirtualDomain which runs fine, but live Migration
does not succeed.
This is the error:

VirtualDomain(vm_snipanalysis)[14322]:  2019/09/18_16:56:54 ERROR: snipanalysis:
live migration to ha-idg-2 failed: 1
Sep 18 16:56:54 [6970] ha-idg-1       lrmd:   notice: operation_finished:      
vm_snipanalysis_migrate_to_0:14322:stderr [ error: operation failed: guest CPU
doesn't match specification: missing features:
fma,movbe,xsave,avx,f16c,rdrand,fsgsbase,bmi1,avx2,smep,bmi2,erms,invpcid,md-clear,xsaveopt,abm
]

The two servers are from HP, they are similar, but not identical. Their
CPU's are different:
One is "Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz", following
/proc/cpuinfo, the other is "Intel(R) Xeon(R) CPU X5675  @ 3.07GHz".
Which guest CPU should i choose for having the guest running smoothly on each
host ?

Bernd

-- 

Bernd Lentes 
Systemadministration 
Institut für Entwicklungsgenetik 
Gebäude 35.34 - Raum 208 
HelmholtzZentrum münchen 
bernd.lentes@helmholtz-muenchen.de 
phone: +49 89 3187 1241 
phone: +49 89 3187 3827 
fax: +49 89 3187 2294 
http://www.helmholtz-muenchen.de/idg 

Perfekt ist wer keine Fehler macht 
Also sind Tote perfekt
 

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir'in Prof. Dr. Veronika von Messling
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

On Wed, Sep 18, 2019 at 05:07:23PM +0200, Lentes, Bernd
wrote:
>Hi,
>
Hello,
>i have atwo node HA-cluster with pacemaker, corosync, libvirt and KVM.
>Recently i configured a new VirtualDomain which runs fine, but live
Migration does not succeed.
>This is the error:
>
>VirtualDomain(vm_snipanalysis)[14322]:  2019/09/18_16:56:54 ERROR:
snipanalysis: live migration to ha-idg-2 failed: 1
>Sep 18 16:56:54 [6970] ha-idg-1       lrmd:   notice: operation_finished:   
vm_snipanalysis_migrate_to_0:14322:stderr [ error: operation failed: guest CPU
doesn't match specification: missing features:
fma,movbe,xsave,avx,f16c,rdrand,fsgsbase,bmi1,avx2,smep,bmi2,erms,invpcid,md-clear,xsaveopt,abm
]
>
>The two servers are from HP, they are similar, but not identical. Their
CPU's are different:
>One is "Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz", following
/proc/cpuinfo, the other is "Intel(R) Xeon(R) CPU X5675  @ 3.07GHz".
>Which guest CPU should i choose for having the guest running smoothly on
each host ?
>
the output of 'virsh domcapabilities' should contain the most
feature-full migratable CPU:
...
    <mode name='host-model' supported='yes'>
      <model fallback='forbid'>Skylake-Client-IBRS</model>
      <vendor>Intel</vendor>
      <feature policy='require' name='ss'/>
      <feature policy='require' name='vmx'/>
      <feature policy='require' name='hypervisor'/>
      <feature policy='require' name='tsc_adjust'/>
      <feature policy='require' name='clflushopt'/>
      <feature policy='require' name='umip'/>
      <feature policy='require' name='md-clear'/>
      <feature policy='require' name='stibp'/>
      <feature policy='require' name='arch-capabilities'/>
      <feature policy='require' name='ssbd'/>
      <feature policy='require' name='xsaves'/>
      <feature policy='require' name='pdpe1gb'/>
      <feature policy='require' name='invtsc'/>
      <feature policy='require'
name='skip-l1dfl-vmentry'/>
    </mode>
...

Running this command on both machines and feeding the concatenated
output to 'virsh hypervisor-cpu-baseline' should give you the
intersection between those CPUs.

Jano