[Users] Fwd: Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
Dear friends, To be rude is not in my intension at all. In case my exprssion have caused you such an impression, please kindly understand that English is not my mother language, and accept my appology. Thanks a lot for you suggestion. I try to check, if the product provdes us with the BIOS switch for NX bit. Best Regards. H.G. 2012/6/14 Andrew Cathrow <acathrow@redhat.com>:
----- Original Message -----
From: "Hideo GOTO" <morpheus.eis@gmail.com> To: users@ovirt.org Sent: Thursday, June 14, 2012 10:27:06 AM Subject: Re: [Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
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".
That sounds a little rude to me, maybe that's not the way you intended it.
Looking at the flags it looks like you are missing NX[1] this might be disabled in the bios, or perhaps not supported in the bios ?
[1] http://en.wikipedia.org/wiki/NX_bit
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@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
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Dear friends, Indeed, your suggestion about NX bit solved our problem. NX bit option on our Proliant server was disabled for god-knows-what-reason. Once the NX bit function is enabled, the processor is now recognized as "Opteron G3", and the 2 HP server nodes were succesfully integrated to a existing production cluster today thanks to all of you. Just FYI, output of "virsh -r capabilities" were giving "Athlon" as CPU model, when NX was disabled. Most of Proliant servers has BIOS switches for NX bit function: "No-Execute Page Protection" for AMD models and "Non-Execute Memory Protection" for Xeon models. HP tells that the these options are enabled by factory default. So, those who get trapped by this mistake as me, should be really minority. Sorry for distubing all of you by such a stupid mistake, and thanks again to all of you. Very best regards. Hideo GOTO 2012/6/14 Hideo GOTO <morpheus.eis@gmail.com>:
Dear friends,
To be rude is not in my intension at all. In case my exprssion have caused you such an impression, please kindly understand that English is not my mother language, and accept my appology.
Thanks a lot for you suggestion. I try to check, if the product provdes us with the BIOS switch for NX bit.
Best Regards.
H.G.
2012/6/14 Andrew Cathrow <acathrow@redhat.com>:
----- Original Message -----
From: "Hideo GOTO" <morpheus.eis@gmail.com> To: users@ovirt.org Sent: Thursday, June 14, 2012 10:27:06 AM Subject: Re: [Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
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".
That sounds a little rude to me, maybe that's not the way you intended it.
Looking at the flags it looks like you are missing NX[1] this might be disabled in the bios, or perhaps not supported in the bios ?
[1] http://en.wikipedia.org/wiki/NX_bit
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@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
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (1)
-
Hideo GOTO