cardo Esteves , 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:
> > >
ne machine.
virsh -r capabilites worked ok at that time
but
virsh capabilites crashed with segfault
-Original Message-
From: Dan Kenigsberg
To: Ricardo Esteves , Justin Clift
Cc: Itamar Heim , users@ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Date:
time
but
virsh capabilites crashed with segfault
-Original Message-
From: Dan Kenigsberg
To: Ricardo Esteves , Justin Clift
Cc: Itamar Heim , 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, 20
[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
To: Itamar Heim , g...@redhat.com
Cc: Ricardo Esteves , users@ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu
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?
__
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.f
e': '18.fc17', 'buildtime':
'1342650221', 'version': '1.0'}}
reservedMem = 321
software_revision = 6
software_version = 4.10
supportedProtocols = ['2.2', '2.3']
supportedRHEVMs = ['3.0', '3.1']
uuid = 37373035-303
2 14:17:44 +0100
CC: users@ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
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)
'qemu-kvm':
{'release': '18.fc17', 'buildtime': '1342650221', 'version': '1.0'},
'libvirt': {'release': '3.fc17', 'buildtime': '1340891887', 'version':
'0.9.11.4'}, &#
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
> /
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,
w
And now, after reboot of the node, i get this:
[root@blade4 ~]# virsh capabilities
Segmentation fault
-Original Message-
From: Ricardo Esteves
To: Itamar Heim
Cc: users@ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Date: Wed, 01 Aug 2012 16:52:11
uot;/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
And now, after reboot of the node, i get this:
[root@blade4 ~]# virsh capabilities
Segmentation fault
-
Original Message-
From: Ricardo Esteves
To: Itamar Heim
Cc: users@ovirt.org
Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Date: Wed, 01 Aug 2012 16:52:11
.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 <mailto:itamar%20heim%20%3cih...@redhat.com%3e>>
;
*To*: Ricardo Esteves 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 Est
kages/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:0000:lib(0):func(0):reason(0)
-----Original Message-
From:
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-
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 Estev
19 matches
Mail list logo
