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

2012-08-12 Thread Dan Kenigsberg
: 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

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

2012-08-10 Thread Ricardo Esteves
, 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

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

2012-08-09 Thread Ricardo Esteves
...@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

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

2012-08-09 Thread Dan Kenigsberg
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?

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

2012-08-09 Thread Ricardo Esteves
: 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

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

2012-08-09 Thread Ricardo Esteves
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

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

2012-08-05 Thread Dan Kenigsberg
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

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

2012-08-02 Thread Justin Clift
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,

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

2012-08-01 Thread Itamar Heim
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

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

2012-08-01 Thread Ricardo Esteves
/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

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

2012-08-01 Thread Itamar Heim
*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

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

2012-08-01 Thread Ricardo Esteves
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 Esteves wrote: [root@blade4 mailto:root@blade4 ~]# vdsClient -s 0 getVdsCaps | grep -i flags