Hi,
oVirt CPU detection depends on libvirt (and that depends on qemu) CPU
models. Could you please run the following command to see what libvirt
reports?
virsh domcapabilities
That should give you the list of CPUs known to libvirt with a usability
flag for each CPU.
If you find out that the CPU is not usable by libvirt, you might want to
dig deeper by querying quemu directly.
Locate any VM running on the system by
sudo virsh list --all
Use the name of a VM in the following command:
sudo virsh qemu-monitor-command [your-vm's-name] --pretty
'{"execute":"query-cpu-definitions"}'
That would give you the list of all CPUs supported by qemu and it will list
all cpu's features that are not available on your system.
Regards,
Lucia
On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users@ovirt.org>
wrote:
> Hi
>
>
>
> I’ve an strange issue with two hosts (not using the hypervisor image) with
> EPYC CPUs, on the engine I got this message:
>
>
>
> The host CPU does not match the Cluster CPU Type and is running in a
> degraded mode. It is missing the following CPU flags: model_EPYC. Please
> update the host CPU microcode or change the Cluster CPU Type.
>
>
>
> But it is an EPYC CPU, the firmware is updated to the latest versions, but
> for some reason oVirt does not like it.
>
>
>
> Here’s the relevant output from VDSM:
>
> "cpuCores": "128",
>
> "cpuFlags":
> "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere",
>
> "cpuModel": "AMD EPYC 7H12 64-Core Processor",
>
> "cpuSockets": "2",
>
> "cpuSpeed": "3293.405",
>
> "cpuThreads": "256",
>
>
>
> Any ideia on why ou what to do to fix it?
>
>
>
> Thanks,
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJVB46MAXKCOA34PEFN576Q/
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OOLJHQDNC4KY4O4B3SJ3PORDKQU6BQM7/
