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

1 Aug 2012

      I didn't disabled anything, but after installing the node when i
configure the option "oVirt Engine" it gives an error saying it can't
download the certificate, but i had this error with previous versions of
the node, and it detected ok the CPU family.

This is the output after a fresh install of the node:

[root@blade4 ~]# vdsClient -s 0 getVdsCaps | grep -i flags
Traceback (most recent call last):
  File "/usr/share/vdsm/vdsClient.py", line 2275, in <module>
  File "/usr/share/vdsm/vdsClient.py", line 403, in do_getCap
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1292, in single_request
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1439, in send_content
  File "/usr/lib64/python2.7/httplib.py", line 954, in endheaders
  File "/usr/lib64/python2.7/httplib.py", line 814, in _send_output
  File "/usr/lib64/python2.7/httplib.py", line 776, in send
  File "/usr/lib/python2.7/site-packages/vdsm/SecureXMLRPCServer.py",
line 91, in connect
  File "/usr/lib64/python2.7/socket.py", line 553, in create_connection
gaierror: [Errno -2] Name or service not known

[root@blade4 ~]# virsh capabilities
<capabilities>

  <host>
    <uuid>35303737-3830-435a-4a30-30333035455a</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Nehalem</model>
      <vendor>Intel</vendor>
      <topology sockets='1' cores='4' threads='2'/>
      <feature name='rdtscp'/>
      <feature name='dca'/>
      <feature name='pdcm'/>
      <feature name='xtpr'/>
      <feature name='tm2'/>
      <feature name='est'/>
      <feature name='vmx'/>
      <feature name='ds_cpl'/>
      <feature name='monitor'/>
      <feature name='dtes64'/>
      <feature name='pbe'/>
      <feature name='tm'/>
      <feature name='ht'/>
      <feature name='ss'/>
      <feature name='acpi'/>
      <feature name='ds'/>
      <feature name='vme'/>
    </cpu>
    <power_management/>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <topology>
      <cells num='1'>
        <cell id='0'>
          <cpus num='8'>
            <cpu id='0'/>
            <cpu id='1'/>
            <cpu id='2'/>
            <cpu id='3'/>
            <cpu id='4'/>
            <cpu id='5'/>
            <cpu id='6'/>
            <cpu id='7'/>
          </cpus>
        </cell>
      </cells>
    </topology>
    <secmodel>
      <model>selinux</model>
      <doi>0</doi>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu-system-x86_64</emulator>
      <machine>pc-0.15</machine>
      <machine>pc-1.0</machine>
      <machine canonical='pc-1.0'>pc</machine>
      <machine>pc-0.14</machine>
      <machine>pc-0.13</machine>
      <machine>pc-0.12</machine>
      <machine>pc-0.11</machine>
      <machine>pc-0.10</machine>
      <machine>isapc</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/bin/qemu-kvm</emulator>
        <machine>pc-0.15</machine>
        <machine>pc-1.0</machine>
        <machine canonical='pc-1.0'>pc</machine>
        <machine>pc-0.14</machine>
        <machine>pc-0.13</machine>
        <machine>pc-0.12</machine>
        <machine>pc-0.11</machine>
        <machine>pc-0.10</machine>
        <machine>isapc</machine>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <pae/>
      <nonpae/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/bin/qemu-system-x86_64</emulator>
      <machine>pc-0.15</machine>
      <machine>pc-1.0</machine>
      <machine canonical='pc-1.0'>pc</machine>
      <machine>pc-0.14</machine>
      <machine>pc-0.13</machine>
      <machine>pc-0.12</machine>
      <machine>pc-0.11</machine>
      <machine>pc-0.10</machine>
      <machine>isapc</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/bin/qemu-kvm</emulator>
        <machine>pc-0.15</machine>
        <machine>pc-1.0</machine>
        <machine canonical='pc-1.0'>pc</machine>
        <machine>pc-0.14</machine>
        <machine>pc-0.13</machine>
        <machine>pc-0.12</machine>
        <machine>pc-0.11</machine>
        <machine>pc-0.10</machine>
        <machine>isapc</machine>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

</capabilities>

When i add the host to oVirt i get this message:

Host blade4.vi.pt moved to Non-Operational state as host does not meet
the cluster's minimum CPU level. Missing CPU features : model_Nehalem

Best regards,
Ricardo Esteves.

-----Original Message-----
From: Itamar Heim <iheim@redhat.com>
To: Ricardo Esteves <ricardo.m.esteves@gmail.com>
Cc: users@ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Date: Wed, 01 Aug 2012 15:43:22 +0300

On 08/01/2012 02:28 PM, Ricardo Esteves wrote:
...
[root@blade4 <mailto:root@blade4> ~]# vdsClient -s 0 getVdsCaps | grep
-i flags
Traceback (most recent call last):
   File "/usr/share/vdsm/vdsClient.py", line 2275, in <module>
   File "/usr/share/vdsm/vdsClient.py", line 403, in do_getCap
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1292, in single_request
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1439, in send_content
   File "/usr/lib64/python2.7/httplib.py", line 954, in endheaders
   File "/usr/lib64/python2.7/httplib.py", line 814, in _send_output
   File "/usr/lib64/python2.7/httplib.py", line 776, in send
   File "/usr/lib/python2.7/site-packages/vdsm/SecureXMLRPCServer.py",
line 98, in connect
   File "/usr/lib64/python2.7/ssl.py", line 381, in wrap_socket
   File "/usr/lib64/python2.7/ssl.py", line 141, in __init__
SSLError: [Errno 0] _ssl.c:340: error:00000000:lib(0):func(0):reason(0)
did you somehow disable ssl?
is vdsm running?
what's its status in engine?

what does this return:
virsh capabilities | grep model
...
-----Original Message-----
*From*: Itamar Heim <iheim@redhat.com
<mailto:Itamar%20Heim%20%3ciheim@redhat.com%3e>>
*To*: Ricardo Esteves <ricardo.m.esteves@gmail.com
<mailto:Ricardo%20Esteves%20%3cricardo.m.esteves@gmail.com%3e>>
*Cc*: users@ovirt.org <mailto:users@ovirt.org>
*Subject*: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
*Date*: Wed, 01 Aug 2012 13:59:27 +0300
On 08/01/2012 12:57 PM, Ricardo Esteves wrote:
...
Hi,
With the latest version of ovirt my host's CPU is not correctly identified,
my host's have an Intel Xeon E5530 (Nehalem family), but is being identified as Conrad family.
My installed versions:
ovirt-engine-3.1.0-2.fc17.noarch
ovirt-node-iso-2.5.0-2.0.fc17.iso
Best regards,
Ricardo Esteves.
_______________________________________________
Users mailing list
Users@ovirt.org  <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
please share:
vdsClient -s 0 getVdsCaps | grep -i flags