5:27 p.m.
Dear Yaniv Kaul,
Thanks for your propmt anwer.
It seems that your patience did not allow your reading to continue
after "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER".
As reported in the last part of my previous mail, the output from
vdsClient shows us that the processor is recognised as none of AMD
Opteron G1, G2 or G3 (cpuFlags=...) . Thus, Quad-core AMD 2384 cannot
match any of Ovirt CPU type options. For confriming, I have just
tried, upon reciept of your reply, to add the host to cluster of other
CPU types (G1, G2 ..) , to get the same unfortunate result.
For your comparaison, here-below shows the "cpuFlags" reported for an
AMD Opteron 4284, which Ovirt can treat as either of AMD Opteron G3,G2
and G1 :
[root@ovnode02 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep cpuFlags
cpuFlags =
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,aperfmperf,pni,pclmulqdq,monitor,ssse3,cx16,sse4_1,sse4_2,popcnt,aes,xsave,avx,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,xop,skinit,wdt,lwp,fma4,nodeid_msr,topoext,perfctr_core,arat,cpb,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_coreduo,model_qemu64,model_core2duo,model_n270,model_Conroe,model_Penryn,model_Nehalem,model_Westmere,model_Opteron_G1,model_Opteron_G2,model_Opteron_G3
2012/6/14 Hideo GOTO <morpheus.eis(a)gmail.com>:
Dear sirs,
We added a HP DL365-G5 server with 2 x "Quad-core AMD Opteron 2384" to
a working ovirt-node cluster ( CPU type of the cluster = "AMD Opteron
G3". Existing node servers use AMD Opteron 4284) . Then, the
Ovirt-engine refuses to intergrate DL365-G5, reporting an error of the
type: "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER".
Ovirt (RHEV) does'nt support AMD Opteron 2xxx series , though they are
KVM compatible? (This HP DL365 worked fine with VMWare).
Any solution, advise, comment is wellcome, since we do not much want
to revirt to VMWare.
FIY, On the ovirt-engine's node information, "CPU Name" is reported as
[N/A] and "CPU Type" as "Quad-Core AMD"
Here below is the content of the /proc/cpuinfo on the HP DL365-G5:
---------------------------------------------------------------------------------
processor : 7
vendor_id : AuthenticAMD
cpu family : 16
model : 4
model name : Quad-Core AMD Opteron(tm) Processor 2384
stepping : 2
microcode : 0x1000086
cpu MHz : 2700.096
cache size : 512 KB
physical id : 1
siblings : 4
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall mmxext
fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl
nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit
wdt npt lbrv svm_lock nrip_save
bogomips : 5400.44
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
---------------------------------------------------------------------------------------
According to vdsClient's info as shown below, Quad-core Opteron is
recognized as if it were a good old 32 bit CPU.
[root@ovnode04 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep cpuFlags
cpuFlags =
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,3dnowext,3dnow,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,pni,monitor,cx16,popcnt,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,skinit,wdt,npt,lbrv,svm_lock,nrip_save,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_athlon
Best RGDS
Hideo GOTO
P.S.
vdsClient tells us : kvmEnabled=true