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`?