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

[Ricardo Esteves]

[root at blade4 ~]# virsh -r cpu-compare /tmp/cpu.xml
Host CPU is a superset of CPU described in /tmp/cpu.xml

-----Original Message-----
From: Dan Kenigsberg <danken at redhat.com>
To: Itamar Heim <iheim at redhat.com>, gal at redhat.com
Cc: Ricardo Esteves <ricardo.m.esteves at gmail.com>, users at ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Date: Thu, 9 Aug 2012 18:57:29 +0300


On Thu, Aug 09, 2012 at 05:17:14PM +0300, Itamar Heim wrote:
> 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?

Interesting...

If yo put
    <cpu match="minimum"><model>Nehalem</model><vendor>Intel</vendor></cpu>
in /tmp/cpu.xml

what does

    virsh -r cpu-compare /tmp/cpu.xml

report?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20120809/4aebf039/attachment-0001.html>