[Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Ricardo Esteves
ricardo.m.esteves at gmail.com
Fri Aug 10 10:18:34 UTC 2012
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.esteves at gmail.com>
To: Dan Kenigsberg <danken at redhat.com>
Cc: Justin Clift <jclift at redhat.com>, Itamar Heim <iheim at redhat.com>,
users at 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 <danken at redhat.com>
To: Ricardo Esteves <ricardo.m.esteves at gmail.com>, Justin Clift
<jclift at redhat.com>
Cc: Itamar Heim <iheim at redhat.com>, users at 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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20120810/63e444b8/attachment-0001.html>
More information about the Users
mailing list