Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification

On 08/09/2012 04:17 PM, Ricardo Esteves wrote: > >Ok, i fixed the ssl problem, my ovirt manager machine iptables was >blocking the 8443 port. > >I also reinstalled the lastest version of the node >(ovirt-node-iso-2.5.1-1.0.fc17.iso), but ovirt manager still doesn't >recognize the CPU. > >The host status remains Non Operational : > >Host localhost.localdomain moved to Non-Operational state as host does >not meet the cluster's minimum CPU level. Missing CPU features : >model_Nehalem danken - libvirt reports nehalem, yet vdsm reports conroe?