Xen + Zaptel in both CentOS 5.2 and 5.1 a no-go

loconut

Joined
Nov 12, 2008
Messages
7
Likes
0
Points
0
#1
I put this in Asterisk since Zaptel is inevitably part of Asterisk. Feel free to move it.

That said, I also apologize if this is re-hashing something, but the posts I found noted the issue but did not resolve it. If a solution is known, I'll be happy to hear it.

I've successfully run Elastix with CentOS 5.1 and 5.2 under VMWare Workstation 6.5 on a Windows XP SP3 32-bit host with an AMD FX-60 64-bit CPU.

I tried to set up Elastix under Xen 3.0.3 (paravirtualized) with a CentOS 5.2 32-bit host (Dell PE2650) and ran into a kernel panic with both CentOS 5.1 and 5.2 running the kernel-xen that was recommended in the how-to. I haven't been able to capture the exact panic because the system toasts the VNC link too fast.

I tried re-compiling the zaptel module to the same effect. If I boot with another kernel that doesn't have Zaptel, everything boots fine, but of course, no zaptel. I don't need any Zaptel card support, but was under the impression the dummy timing thing was important.

Has anyone come up with a solid solution/combination of kernel and zaptel and xen 3.0.3 (paravirt) to make things work?
 

naderp

Joined
Nov 15, 2008
Messages
4
Likes
0
Points
0
#2
same probleme here... and I'm puzzled because I've even tried a known working kernel/zaptel combination and that fails too.:S

Some people have suggested passing a PCI card clock timing sourcebut that's not an option for me as I want a pure VoIP setup.

I'm willing to give anything else a go if anyone has any suggestions - cheers

Here's the kernel dump, hpoing it sheds some light:

Loading zaptel hardware modules:
No hardware timing source found in /proc/zaptel, loading ztdummy
------------[ cut here ]------------
kernel BUG at kernel/timer.c:331!
invalid opcode: 0000 [#1]
SMP
last sysfs file: /class/zaptel/zapctl/dev
Modules linked in: ztdummy(U) zaptel(U) oslec(U) crc_ccitt dm_multipath parport_pc lp parport pcspkr dm_snapshot dm_zero dm_mirror dm_mod xenblk ext3 jbd ehci_hcd ohci_hcd uhci_hcd
CPU: 0
EIP: 0061:[<c0424663>] Tainted: GF VLI
EFLAGS: 00010046 (2.6.18-53.1.19.el5xen #1)
EIP is at __mod_timer+0x11/0xa3
eax: c07a1c34 ebx: 00000000 ecx: fffef5cf edx: fffef5d4
esi: c07a1c34 edi: c7ee9000 ebp: fffef5d4 esp: c07d3e20
ds: 007b es: 007b ss: 0069
Process modprobe (pid: 850, ti=c07d3000 task=c7e19aa0 task.ti=c07d3000)
Stack: c075cefd 0000001d 00000000 000000fa c7ee9000 c02dd368 c052ea1e c71490c0
c0496d2f 00000000 c71490c0 00008000 00000001 c0497167 c70e70c0 c07d3eab
c7ee9000 c9162d24 c07d3eab c91653e6 00000001 00000000 ffffffff ffffffff
Call Trace:
[<c052ea1e>] rtc_do_ioctl+0x18f/0x6aa
[<c0496d2f>] proc_register+0x74/0xfc
[<c0497167>] create_proc_entry+0x8b/0x9e
[<c9162d24>] zt_register+0x155/0x23a [zaptel]
[<c041d4b3>] printk+0x19/0x9c
[<c05fd198>] _spin_lock_irqsave+0x8/0x28
[<c9118284>] init_module+0x16e/0x1e5 [ztdummy]
[<c0434f9d>] sys_init_module+0x16ff/0x1882
[<c04671f9>] do_sync_read+0x0/0xf1
[<c0467bb8>] vfs_read+0x9f/0x141
[<c040534f>] syscall_call+0x7/0xb
=======================
Code: 89 f0 5a 5b 5e c3 53 89 c3 89 d8 e8 ac ff ff ff 85 c0 79 04 f3 90 eb f1 5b c3 55 89 d5 57 56 89 c6 53 83 ec 08 83 78 0c 00 75 08 <0f> 0b 4b 01 12 8f 61 c0 8d 54 24 04 89 f0 e8 4f ff ff ff 8b 16
EIP: [<c0424663>] __mod_timer+0x11/0xa3 SS:ESP 0069:c07d3e20
<0>Kernel panic - not syncing: Fatal exception
BUG: warning at arch/i386/kernel/smp-xen.c:529/smp_call_function() (Tainted: GF )
[<c040e703>] smp_call_function+0x59/0xfe
[<c040e7bb>] smp_send_stop+0x13/0x1e
[<c041ca57>] panic+0x4c/0x175
[<c0405fc3>] die+0x267/0x29b
[<c0406513>] do_invalid_op+0x0/0x9d
[<c04065a4>] do_invalid_op+0x91/0x9d
[<c0424663>] __mod_timer+0x11/0xa3
[<c0416b20>] enqueue_task+0x13/0x39
[<c0407f3c>] monotonic_clock+0x45/0x94
[<c05fba42>] schedule+0x736/0x7b7
[<c04054d3>] error_code+0x2b/0x30
[<c0424663>] __mod_timer+0x11/0xa3
[<c052ea1e>] rtc_do_ioctl+0x18f/0x6aa
[<c0496d2f>] proc_register+0x74/0xfc
[<c0497167>] create_proc_entry+0x8b/0x9e
[<c9162d24>] zt_register+0x155/0x23a [zaptel]
[<c041d4b3>] printk+0x19/0x9c
[<c05fd198>] _spin_lock_irqsave+0x8/0x28
[<c9118284>] init_module+0x16e/0x1e5 [ztdummy]
[<c0434f9d>] sys_init_module+0x16ff/0x1882
[<c04671f9>] do_sync_read+0x0/0xf1
[<c0467bb8>] vfs_read+0x9f/0x141
[<c040534f>] syscall_call+0x7/0xb
=======================
[root@pstnserver ~]#
 

seaq

Joined
Sep 17, 2008
Messages
41
Likes
0
Points
0
#3
I'm taking the same trouble. I've installed Elastix 1.3 on a Xen VM, and it works fine except zaptel and ztdummy.

When I start the Xen machine Elastix with zaptel active, the system crashes inmediately. I've deactivated zaptel with "chkconfig zaptel off" and i've rebooted the system; and it boots without problems.

I found a possible solution for this issue in the following link:

http://www.odindev.com/troubles-zaptel- ... n-asterisk

Thanks for your help.
 

seaq

Joined
Sep 17, 2008
Messages
41
Likes
0
Points
0
#4
Yes;

Zaptel, and ztdummy, are working successfully on my VM Xen Elastix after to apply the link's instructions.

:-]
 

a_villacis

Joined
Jun 2, 2008
Messages
36
Likes
0
Points
0
#5

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#6

torontob

Joined
May 18, 2008
Messages
219
Likes
0
Points
0
#7
Are there any instructions posted on how to install Elastix on Amazon Ec2? I have noticed the Voxilla post as well for vanilla Asterisk. However, I am wondering if Amazon even provides a reliable system?

Can anyone comment on this please?

Thanks,
Bruce
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,887
Members
17,566
Latest member
Fpino
Top