Asterisk on a virtual machine via OpenStack?

Question

Asterisk

Colleagues, good afternoon.
There was a problem starting Asterisk.
The essence of the problem: After successful (?) compilation and installation, when trying to run, we get:

asterisk exited on signal 4

I’ll make a reservation right away : all the actions described below were performed with versions 10.9, 10.10, 11.

The Ubuntu Cloud 12.04.1 image with kernel version 3.2.0-32-virtual was raised using qemu and kvm using OpenStack.
/proc/cpuinfo host machines:

model name	: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid

/proc/meminfo host machines:

MemTotal:       24659712 kB
MemFree:        11321680 kB

Excerpts from the guest machine:

model name	: Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
flags		: fpu pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc rep_good nopl pni monitor cx16 popcnt hypervisor lahf_lm

MemTotal:        2051652 kB
MemFree:         1149676 kB

We will leave the characteristics of the processor and supported instructions transferred to the guest machine to the conscience of nova-compute. Taking into account the launch parameters of the virtualization process itself, the developers have hardwired these settings into code, which is unreasonable to change in the context of constant package updates. But if suddenly I am mistaken and someone will correct me, I will be overly grateful.

Dahdi-linux-complete is built and installed.

So, the configuration script was run in two modes:

./configure
./configure CFLAGS="-march=core2" CXXFLAGS="--march core2"

launch

make menuselect

without any changes, everything is default.
After we do:

make
make install
make samples
make config

Next, we try to start the process either on behalf of the root, or on behalf of the asterisk user.
We start with options:

safe_asterisk
service asterisk start
asterisk -cvvvvv
/etc/init.d/asterisk start

In the case of -cvvvvv, the asterisk correctly reads the configs, but does not get to the end of the launch. It is impossible to determine exactly where the process "stumbles": each time, depending on the load of the machine, it breaks in different places. The time before the interruption of the process was measured by means of time. No dependencies installed.
As a result, we get:

asterisk exited on signal 4

And an endless restart. Singal 4 is SIGILL
, which has already become hated for me. I will be grateful for any hints, options. I'm asking for help after three days of hard googling.

Answer 1

Native Build in menuconf off

Answer 2

1) strace asterisk -cvvvv
2) asterisk -cvvvdddg
-g Dump core in case of a crash

Answer 3

As far as I understand, you don’t need Dahdi-linux-complete at all, I advise you to remove everything related to it from make menuselect, and also disable unnecessary modules! I can email you what can be removed without any problems