[Users] Missing CPU features [CPU Name] [Wrong cpu identification]
I added Host[gondor] to the oVirt Engine 3.1, after installing all packages. Host gondor moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem This Box is a Intel(R) Xeon(TM) CPU 3.00GHz - Intel Nehalem Family - so I modified/added the caps.py (/usr/share/vdsm). Line 107--> def _getCompatibleCpuModels(): return ["model_Nehalem"] (this is what i added). Now after restart de service the Host status remains UP. Can you report it?? To fix this. Thanks. Pere Soria pere at onda.es
On 12/13/2012 01:14 PM, Pere G. Soria wrote:
I added Host[gondor] to the oVirt Engine 3.1, after installing all packages. Host gondor moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem
This Box is a Intel(R) Xeon(TM) CPU 3.00GHz - Intel Nehalem Family - so I modified/added the caps.py (/usr/share/vdsm). Line 107--> def _getCompatibleCpuModels(): return ["model_Nehalem"] (this is what i added).
Now after restart de service the Host status remains UP.
Can you report it?? To fix this.
Do you have everything enabled in BIOS for the processor (AES, NX)? I don't understand what the "Missing CPU features : model_Nehalem" should mean, but if you check what features you have in /proc/cpuinfo, most probably there will be something missing. Martin
On 12/13/2012 02:55 PM, Martin Kletzander wrote:
On 12/13/2012 01:14 PM, Pere G. Soria wrote:
I added Host[gondor] to the oVirt Engine 3.1, after installing all packages. Host gondor moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem
This Box is a Intel(R) Xeon(TM) CPU 3.00GHz - Intel Nehalem Family - so I modified/added the caps.py (/usr/share/vdsm). Line 107--> def _getCompatibleCpuModels(): return ["model_Nehalem"] (this is what i added).
Now after restart de service the Host status remains UP.
Can you report it?? To fix this.
Do you have everything enabled in BIOS for the processor (AES, NX)? I don't understand what the "Missing CPU features : model_Nehalem" should mean, but if you check what features you have in /proc/cpuinfo, most probably there will be something missing.
martin - missing CPU feature: model_Nehalem means libvirt didn't report nehalem as a support cpu model for this machine.
On 12/13/2012 04:27 PM, Itamar Heim wrote:
On 12/13/2012 02:55 PM, Martin Kletzander wrote:
On 12/13/2012 01:14 PM, Pere G. Soria wrote:
I added Host[gondor] to the oVirt Engine 3.1, after installing all packages. Host gondor moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem
This Box is a Intel(R) Xeon(TM) CPU 3.00GHz - Intel Nehalem Family - so I modified/added the caps.py (/usr/share/vdsm). Line 107--> def _getCompatibleCpuModels(): return ["model_Nehalem"] (this is what i added).
Now after restart de service the Host status remains UP.
Can you report it?? To fix this.
Do you have everything enabled in BIOS for the processor (AES, NX)? I don't understand what the "Missing CPU features : model_Nehalem" should mean, but if you check what features you have in /proc/cpuinfo, most probably there will be something missing.
martin - missing CPU feature: model_Nehalem means libvirt didn't report nehalem as a support cpu model for this machine. /usr/share/libvirt/cpu_map.xml maps the machine cpu flags to a supported model. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 12/13/2012 04:48 PM, Roy Golan wrote:
On 12/13/2012 04:27 PM, Itamar Heim wrote:
On 12/13/2012 02:55 PM, Martin Kletzander wrote:
On 12/13/2012 01:14 PM, Pere G. Soria wrote:
I added Host[gondor] to the oVirt Engine 3.1, after installing all packages. Host gondor moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem
This Box is a Intel(R) Xeon(TM) CPU 3.00GHz - Intel Nehalem Family - so I modified/added the caps.py (/usr/share/vdsm). Line 107--> def _getCompatibleCpuModels(): return ["model_Nehalem"] (this is what i added).
Now after restart de service the Host status remains UP.
Can you report it?? To fix this.
Do you have everything enabled in BIOS for the processor (AES, NX)? I don't understand what the "Missing CPU features : model_Nehalem" should mean, but if you check what features you have in /proc/cpuinfo, most probably there will be something missing.
martin - missing CPU feature: model_Nehalem means libvirt didn't report nehalem as a support cpu model for this machine. /usr/share/libvirt/cpu_map.xml maps the machine cpu flags to a supported model.
easy to check, does "vdsClient -s 0 getVdsCaps | grep -i flag" returns model_Nehalem? if so, maybe a bug in engine side comparison searching for this model?
On 12/13/2012 03:27 PM, Itamar Heim wrote:
On 12/13/2012 02:55 PM, Martin Kletzander wrote:
On 12/13/2012 01:14 PM, Pere G. Soria wrote:
I added Host[gondor] to the oVirt Engine 3.1, after installing all packages. Host gondor moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem
This Box is a Intel(R) Xeon(TM) CPU 3.00GHz - Intel Nehalem Family - so I modified/added the caps.py (/usr/share/vdsm). Line 107--> def _getCompatibleCpuModels(): return ["model_Nehalem"] (this is what i added).
Now after restart de service the Host status remains UP.
Can you report it?? To fix this.
Do you have everything enabled in BIOS for the processor (AES, NX)? I don't understand what the "Missing CPU features : model_Nehalem" should mean, but if you check what features you have in /proc/cpuinfo, most probably there will be something missing.
martin - missing CPU feature: model_Nehalem means libvirt didn't report nehalem as a support cpu model for this machine.
Oh, OK, thanks for the info. So I answered properly :) Let's see if we'll find out something from the /proc/cpuinfo. It looks very similar to those issues mentioned on the libvirt wiki [1] and others often discussed, so I'm fairly sure that'll be the issue. [1] http://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_differen...
participants (4)
-
Itamar Heim -
Martin Kletzander -
Pere G. Soria -
Roy Golan