CPU model: x86_64CPU(s): 112CPU frequency: 4000 MHzCPU socket(s): 1Core(s) per socket: 28Thread(s) per core: 2NUMA cell(s): 2Memory size: 4144275952 KiB
<cpu><arch>x86_64</arch><model>Cascadelake-Server-noTSX</model><vendor>Intel</vendor><microcode version='83899138'/><counter name='tsc' frequency='2199999000' scaling='yes'/><topology sockets='1' dies='1' cores='28' threads='2'/><topology><cells num='2'><cell id='0'><memory unit='KiB'>4144275952</memory><cpus num='56'>
"cpuCores": "56","cpuFlags": "ds_cpl,epb,aperfmperf,xsaveopt,cx8,cat_l3,smx,x2apic,invpcid_single,mmx,rdseed,est,sse4_2,clwb,umip,apic,ss,ida,pbe,xsavec,sdbg,mca,bmi1,pat,tsc_deadline_timer,sep,lahf_lm,avx,cqm_mbm_local,sse2,hypervisor,pku,sse,ibrs_enhanced,md_clear,nx,aes,msr,invpcid,rep_good,avx2,fxsr,pse36,amd-ssbd,de,ssbd,tsc_adjust,cqm,pae,avx512f,bts,vmx,rdctl-no,dtes64,lm,ospke,fma,mtrr,pdpe1gb,pcid,acpi,movbe,nonstop_tsc,pln,xsaves,amd-stibp,pschange-mc-no,avx512dq,ht,pdcm,cpuid_fault,smep,3dnowprefetch,tsc,avx512vl,xtopology,skip-l1dfl-vmentry,pebs,intel_ppin,flush_l1d,art,popcnt,abm,monitor,arch-capabilities,cpuid,fsgsbase,rdt_a,syscall,bmi2,ssse3,stibp,tsx-ctrl,smap,constant_tsc,sse4_1,erms,cmov,pge,xsave,cx16,ibpb,avx512_vnni,vme,arch_capabilities,nopl,cdp_l3,tm2,dca,invtsc,cqm_mbm_total,rdtscp,xgetbv1,rdrand,adx,cqm_llc,tpr_shadow,pclmulqdq,ept,xtpr,vpid,avx512bw,cqm_occup_llc,ept_ad,pts,mba,pse,tm,dts,clflush,mce,intel_pt,f16c,clflushopt,ibrs-all,arch_perfmon,avx512cd,ibrs,md-clear,mds-no,arat,dtherm,fpu,pni,mpx,vnmi,flexpriority,spec_ctrl,model_SandyBridge-IBRS,model_Nehalem-IBRS,model_Opteron_G2,model_Westmere,model_Skylake-Client-noTSX-IBRS,model_Conroe,model_coreduo,model_qemu64,model_IvyBridge-IBRS,model_Skylake-Server-noTSX-IBRS,model_kvm32,model_pentium3,model_pentium,model_Westmere-IBRS,model_SandyBridge,model_Nehalem,model_Penryn,model_kvm64,model_Haswell-noTSX,model_486,model_Cascadelake-Server-noTSX,model_Opteron_G1,model_core2duo,model_pentium2,model_IvyBridge,model_Broadwell-noTSX-IBRS,model_qemu32,model_n270,model_Haswell-noTSX-IBRS,model_Broadwell-noTSX","cpuModel": "Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz","cpuSockets": "1","cpuSpeed": "4000.000","cpuThreads": "112","numaNodes": {"0": {"cpus": [56,57,.,.,110,111],"hugepages": {},"totalMemory": "2023136"}},"onlineCpus": "0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111"
Hi,
could you check
sudo vdsm-client Host getCapabilities
virsh nodeinfo
virsh capabilities
and possibly see the issue?
By the way most likely I think you will see CPU socket(s): 1 in virsh nodeinfo, but with NUMA cell(s): 2
(that will be OK)
BR,
Konstantin
Von: Jorge Visentini <jorgevisentini@gmail.com>
Datum: Dienstag, 27. Juni 2023 um 18:50
An: Dean L <dean@datacom.ca>
Cc: "users@ovirt.org" <users@ovirt.org>
Betreff: [ovirt-users] Re: Processors compatibility matrix oVirt
Sorry, I mentioned it wrong. The engine VM is ok. What happens is that the lscpu output of the physical host is different from the host information in oVirt.
lscpu:
CPU(s): 112
On-line CPU(s) list: 0-111
Thread(s) per core: 2
Core(s) per socket: 28
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
BIOS Vendor ID: Intel(R) Corporation
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz
Ovirt -> Compute -> Hosts:
CPU Model Name: Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz
CPU Type: Secure Intel Cascadelake Server Family
CPU Sockets: 1
CPU Cores per Socket: 56
CPU Threads per Core: 2 (SMT Enabled)
TSC Frequency: 2199999000 (scaling enabled)
Em ter., 27 de jun. de 2023 às 12:22, Dean L via Users <users@ovirt.org> escreveu:
Jorge,
Your 8276 processor belongs to the former Cascade Lake Family (server), which is supported by oVirt (listed as Intel Cascadelake Server Family).
For CPU requirements see: https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/#CPU_Requirements_SM_remoteDB_deploy
In Linux, you can see the number of sockets with: grep "physical id" /proc/cpuinfo | sort -u | wc -l
Not sure how you installed your oVirt engine, but with hosted-engine, oVirt installs with 1 virtual socket and in advanced options can be change to 2 or 4.
Cheers!
... Dean
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/7Q6U4T2CVHQV4HSB57GMCDYN22OOJRVB/
--
Att,
Jorge Visentini
+55 55 98432-9868