[asterisk-bugs] [JIRA] Commented: (ASTERISK-20128) Virtualized asterisk.org 1.8.14.0 no longer runs in a KVM virtualized environment. Compiles without error, but fails with Illegal instruction on launch Regression since 1.8.13.0 Last good 1.8.12.2

Kinsey Moore (JIRA) noreply at issues.asterisk.org
Fri Jul 20 13:22:21 CDT 2012


    [ https://issues.asterisk.org/jira/browse/ASTERISK-20128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195064#comment-195064 ] 

Kinsey Moore commented on ASTERISK-20128:
-----------------------------------------

Having a system I can get into would work.  If not, you can run Asterisk in GDB until it crashes and then disassemble the code and find the address where it threw the SIGILL.  What are the CPU flags for the non-virtualized install on that machine?  Do they differ from the forced CPU option?  You can send the connection info to kmoore at digium.com if you go that route.

> Virtualized asterisk.org 1.8.14.0  no longer runs in a KVM virtualized environment.     Compiles without error,  but fails with Illegal instruction on launch  Regression since 1.8.13.0     Last good 1.8.12.2  
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20128
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20128
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: .Release/Targets
>    Affects Versions: 1.8.13.0, 1.8.14.0
>         Environment: verified on Centos 6.2 and 6.3 - 64 bit
> running in KVM virtualized instances with the following  /proc/cpuinfo 
> processor	: 0
> vendor_id	: AuthenticAMD
> cpu family	: 6
> model		: 2
> model name	: QEMU Virtual CPU version 0.15.1
> stepping	: 3
> cpu MHz		: 1497.505
> cache size	: 512 KB
> fpu		: yes
> fpu_exception	: yes
> cpuid level	: 4
> wp		: yes
> flags		: fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm up unfair_spinlock pni cx16 popcnt hypervisor lahf_lm svm abm sse4a
> bogomips	: 2995.01
> TLB size	: 1024 4K pages
> clflush size	: 64
> cache_alignment	: 64
> address sizes	: 40 bits physical, 48 bits virtual
> power management:
>            Reporter: linux ninja1
>            Assignee: Kinsey Moore
>         Attachments: cat-proc-cpuinfo-with-different-settings.txt, console-logfile.txt, KVM-Virt-Manager-defaults.png, KVM-Virt-Manager-forced-CPU.png
>
>
> We are running asterisk 1.8.X instances in virtual machines.
> The asterisk virtual machines are running Centos 6.2 and 6.3.
> Kernel of virtual machines is :  2.6.32-279.1.1.el6.x86_64 #1 SMP Tue Jul 10 13:47:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> KVM Hypervisor / host is a Fedora 16 with the latest kernel :  3.4.4-4.fc16.x86_64 #1 SMP Thu Jul 5 20:01:38 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Hardware is HP ProLiant N40L  MicroServer 
> Any asterisk version higher than 1.8.12.2 fails with a "illegal instruction" on launch of asterisk.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list