# OpenNebula Setup: One VM + 2 Physicals: Program terminated with signal 11, Segmentation fault **URL:** \ **Category:** Product Support\ **Created:** [March 25, 2018, 8:36pm UTC](https://forum.opennebula.io/t/opennebula-setup-one-vm-2-physicals-program-terminated-with-signal-11-segmentation-fault/5843 "2018-03-25T20:36:13Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![TomK](https://avatars.discourse-cdn.com/v4/letter/t/ee59a6/32.png) [@TomK](https://forum.opennebula.io/u/TomK)\ **Post date:** [March 25, 2018, 8:55pm UTC](https://forum.opennebula.io/t/opennebula-setup-one-vm-2-physicals-program-terminated-with-signal-11-segmentation-fault/5843/3 "2018-03-25T20:55:49Z")
I see another has the same issue. I can also keep reproducing this issue: The second thread by someone else is: > [@Oned process segfault (error 4 in libc-2.17.so)](https://forum.opennebula.io/t/oned-process-segfault-error-4-in-libc-2-17-so/2591): > > Hi, all Recently I’ve started using latest OpenNebula 5.0.1 2-node HA cluster (corosync + pacemaker) with the CEPH “Jewel” backend and everything works as expected, but I’ve met a strange issue with the instability of the “oned” process, when it randomly crashes on two completely different hardware platforms. Ok, I have two hosts with the same OS - CentOS 7.2 x86\_64: uname -a Linux 4.6.3-1.el7.elrepo.x86\_64 #1 SMP x86\_64 GNU/Linux But with different hardware: [root@nebula-1 ~]# lspci 00:0… Cheers, Tom --- _[View the full topic](https://forum.opennebula.io/t/opennebula-setup-one-vm-2-physicals-program-terminated-with-signal-11-segmentation-fault/5843)._