On Thu, May 28, 2020 at 3:01 PM Lucia Jelinkova <ljelinko@redhat.com> wrote:
It is really strange, the host should not even be in UP state if it does not comply with the cluster cpu type settings.

Would you mind sharing the engine.log?

And if that's not much of a trouble, could you have a look into the database?

select cpu_flags from vds_dynamic;
select name, cpu_name, cpu_flags, cpu_verb from cluster;

Thanks,

Lucia

engine.log.gz here:
https://drive.google.com/file/d/1fclwgYhFUU1qgFodv4V_sQauIvmMvSS2/view?usp=sharing


cpu_flags | mce,xsavec,sep,fma,rtm,xgetbv1,arat,lm,mpx,tsc,avx512vl,avx512f,ssbd,avx,vpid,pdpe1gb,cpuid,vme,tsc_deadline_timer,avx2,mca,clwb,tsc_adjust,lahf_lm,ibrs,pcid,erms,x2apic,skip-l1dfl-vmentry,de,sse4_2,msr,syscall,invpcid,clflushopt,pat,sse4_1,avx512_vnni,hypervisor,fsgsbase,nopl,xsaveopt,vmx,md-clear,ibpb,pae,md_clear,pse36,pclmulqdq,avx512dq,movbe,hle,adx,rep_good,3dnowprefetch,bmi1,bmi2,avx512bw,umip,mtrr,pni,xsave,pse,vnmi,fxsr,aes,popcnt,rdtscp,rdseed,sse2,avx512cd,cx8,smap,nx,invpcid_single,arch-capabilities,arch_perfmon,ibrs-all,rdrand,abm,tsc_known_freq,mds-no,apic,rdctl-no,cmov,stibp,smep,mmx,constant_tsc,pge,pku,ss,ospke,clflush,tpr_shadow,cx16,ssse3,ept,xtopology,ht,arch_capabilities,flexpriority,fpu,f16c,sse,ibrs_enhanced,model_kvm64,model_Skylake-Server,model_core2duo,model_Opteron_G2,model_Skylake-Server-IBRS,model_Broadwell,model_Haswell,model_kvm32,model_IvyBridge-IBRS,model_Cascadelake-Server,model_Nehalem-IBRS,model_Broadwell-IBRS,model_qemu64,model_qemu32,model_Haswell-noTSX,model_Nehalem,model_pentium,model_SandyBridge,model_IvyBridge,model_Westmere-IBRS,model_Haswell-IBRS,model_Westmere,model_Broadwell-noTSX,model_Skylake-Client-IBRS,model_pentium3,model_coreduo,model_486,model_Skylake-Client,model_Haswell-noTSX-IBRS,model_Broadwell-noTSX-IBRS,model_Conroe,model_n270,model_pentium2,model_SandyBridge-IBRS,model_Penryn,model_Opteron_G1

for the cluster type in the mean time I was able to change it to "Intel Cascadelake Server Family" from web admin gui and now I have to try these steps and see if engine starts automatically without manual operations

1) set global maintenance
2) shutdown engine
3) exit maintenance
4) see if the engine vm starts without the cpu flag....

so the query returns now:

engine=# select name, cpu_name, cpu_flags, cpu_verb from cluster;
-[ RECORD 1 ]----------------------------------------------
name      | Default
cpu_name  | Intel Cascadelake Server Family
cpu_flags | vmx,model_Cascadelake-Server
cpu_verb  | Cascadelake-Server,-hle,-rtm,+arch-capabilities


Gianluca