Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
On Thu, Aug 09, 2012 at 05:22:09PM +0100, Ricardo Esteves wrote: [root@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 dan...@redhat.com To: Itamar Heim ih...@redhat.com, g...@redhat.com Cc: Ricardo Esteves ricardo.m.este...@gmail.com, users@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=minimummodelNehalem/modelvendorIntel/vendor/cpu in /tmp/cpu.xml what does virsh -r cpu-compare /tmp/cpu.xml report? (top posting make it very difficult to follow a long thread) I have a hunch that this is something that has been fixed by http://gerrit.ovirt.org/#/c/5035/ Find vendor for all cpu models, including those based on another cpu module. it is accpeted upstream, but unfortunately did not make it into the ovirt-3.1 release. Could you apply the patch to Vdsm and see if it fixes the reported cpu level? Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Ok, i reinstalled the host to try to reproduce the problem. I blocked again the 8443 on ovirt manager machine. Configured the ovirt engine options on the host and gave me the error that couldn't download the certificate. I run virsh capabilities and worked ok. Then i rebooted the host and now when i run virsh capabilities it gives me segfault. On dmesg i get this message: virsh -r capabilities runs ok. -Original Message- From: Ricardo Esteves ricardo.m.este...@gmail.com To: Dan Kenigsberg dan...@redhat.com Cc: Justin Clift jcl...@redhat.com, Itamar Heim ih...@redhat.com, users@ovirt.org Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification Date: Thu, 09 Aug 2012 17:31:30 +0100 Now it's difficult to reproduce the problem, unless i install the host again. The problem seemed to be, when i configured the ovirt engine options on the host it failed to download the certificate because port 8443 was blocked on ovirt engine machine. virsh -r capabilites worked ok at that time but virsh capabilites crashed with segfault -Original Message- From: Dan Kenigsberg dan...@redhat.com To: Ricardo Esteves ricardo.m.este...@gmail.com, Justin Clift jcl...@redhat.com Cc: Itamar Heim ih...@redhat.com, users@ovirt.org Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification Date: Thu, 9 Aug 2012 19:00:42 +0300 On Thu, Aug 09, 2012 at 02:17:44PM +0100, Ricardo Esteves wrote: Ok, i fixed the ssl problem, my ovirt manager machine iptables was blocking the 8443 port. Neither issue is a good-enough reason for virsh to segfault. Could you provide more information so that some can solve that bug? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
/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 modelselinux/model doi0/doi /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/bin/qemu-system-x86_64/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine domain type='qemu' /domain domain type='kvm' emulator/usr/bin/qemu-kvm/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine /domain /arch features cpuselection/ deviceboot/ pae/ nonpae/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest guest os_typehvm/os_type arch name='x86_64' wordsize64/wordsize emulator/usr/bin/qemu-system-x86_64/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine domain type='qemu' /domain domain type='kvm' emulator/usr/bin/qemu-kvm/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest /capabilities - Original Message- From: Dan Kenigsberg dan...@redhat.com To: Justin Clift jcl...@redhat.com Cc: Ricardo Esteves maverick...@gmail.com, users@ovirt.org Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification Date: Sun, 5 Aug 2012 11:18:25 +0300 On Fri, Aug 03, 2012 at 06:47:44AM +1000, Justin Clift wrote: On 02/08/2012, at 2:29 AM, Ricardo Esteves wrote: And now, after reboot of the node, i get this: [root@blade4 ~]# virsh capabilities Segmentation fault When that seg fault happens, does anything get printed to /var/log/messages? Kind of wondering if there's something else at play here, which might show up there. Worth a look at. :) Regards and best wishes, Justin Clift Please note that vdsm hacks libvirt to use sasl authentication, which may be related to this crash. Does anything look better with `virsh -r`? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
On Thu, Aug 09, 2012 at 02:17:44PM +0100, Ricardo Esteves wrote: Ok, i fixed the ssl problem, my ovirt manager machine iptables was blocking the 8443 port. Neither issue is a good-enough reason for virsh to segfault. Could you provide more information so that some can solve that bug? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
[root@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 dan...@redhat.com To: Itamar Heim ih...@redhat.com, g...@redhat.com Cc: Ricardo Esteves ricardo.m.este...@gmail.com, users@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=minimummodelNehalem/modelvendorIntel/vendor/cpu in /tmp/cpu.xml what does virsh -r cpu-compare /tmp/cpu.xml report? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Now it's difficult to reproduce the problem, unless i install the host again. The problem seemed to be, when i configured the ovirt engine options on the host it failed to download the certificate because port 8443 was blocked on ovirt engine machine. virsh -r capabilites worked ok at that time but virsh capabilites crashed with segfault -Original Message- From: Dan Kenigsberg dan...@redhat.com To: Ricardo Esteves ricardo.m.este...@gmail.com, Justin Clift jcl...@redhat.com Cc: Itamar Heim ih...@redhat.com, users@ovirt.org Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification Date: Thu, 9 Aug 2012 19:00:42 +0300 On Thu, Aug 09, 2012 at 02:17:44PM +0100, Ricardo Esteves wrote: Ok, i fixed the ssl problem, my ovirt manager machine iptables was blocking the 8443 port. Neither issue is a good-enough reason for virsh to segfault. Could you provide more information so that some can solve that bug? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
On Fri, Aug 03, 2012 at 06:47:44AM +1000, Justin Clift wrote: On 02/08/2012, at 2:29 AM, Ricardo Esteves wrote: And now, after reboot of the node, i get this: [root@blade4 ~]# virsh capabilities Segmentation fault When that seg fault happens, does anything get printed to /var/log/messages? Kind of wondering if there's something else at play here, which might show up there. Worth a look at. :) Regards and best wishes, Justin Clift Please note that vdsm hacks libvirt to use sasl authentication, which may be related to this crash. Does anything look better with `virsh -r`? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
On 02/08/2012, at 2:29 AM, Ricardo Esteves wrote: And now, after reboot of the node, i get this: [root@blade4 ~]# virsh capabilities Segmentation fault When that seg fault happens, does anything get printed to /var/log/messages? Kind of wondering if there's something else at play here, which might show up there. Worth a look at. :) Regards and best wishes, Justin Clift -- Aeolus Community Manager http://www.aeolusproject.org ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
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 http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
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 http://lists.ovirt.org/mailman/listinfo/users please share: vdsClient -s 0 getVdsCaps | grep -i flags ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
[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::lib(0):func(0):reason(0) -Original Message- From: Itamar Heim ih...@redhat.com To: Ricardo Esteves ricardo.m.este...@gmail.com Cc: 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 http://lists.ovirt.org/mailman/listinfo/users please share: vdsClient -s 0 getVdsCaps | grep -i flags ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
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::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 ih...@redhat.com mailto:itamar%20heim%20%3cih...@redhat.com%3e *To*: Ricardo Esteves ricardo.m.este...@gmail.com mailto:ricardo%20esteves%20%3cricardo.m.este...@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
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 uuid35303737-3830-435a-4a30-30333035455a/uuid cpu archx86_64/arch modelNehalem/model vendorIntel/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_transporttcp/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 modelselinux/model doi0/doi /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/bin/qemu-system-x86_64/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine domain type='qemu' /domain domain type='kvm' emulator/usr/bin/qemu-kvm/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine /domain /arch features cpuselection/ deviceboot/ pae/ nonpae/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest guest os_typehvm/os_type arch name='x86_64' wordsize64/wordsize emulator/usr/bin/qemu-system-x86_64/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine domain type='qemu' /domain domain type='kvm' emulator/usr/bin/qemu-kvm/emulator machinepc-0.15/machine machinepc-1.0/machine machine canonical='pc-1.0'pc/machine machinepc-0.14/machine machinepc-0.13/machine machinepc-0.12/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/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 ih...@redhat.com To: Ricardo Esteves ricardo.m.este...@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
