Hi,
I've tried to run Asterisk 1.2 from backports.org inside Xen 3.0.2 VM
For my own doesn't works ...
As you know the problem come from ztdummy driver that use RTC
and this driver is required for "conference" module ...
If I load "rtc.ko" inside dom0 and if I start a domU it tell that
IRQ
8 is not free ...
If I try to load it directly in a domU with ztdummy.ko I obtain this
----------------------
Zaptel cards initial configuration: Zapata Telephony Interface
Registered on major 196
Zaptel Version: 1.2.7 Echo Canceller: KB1
general protection fault: 0000 [#1]
SMP
Modules linked in: zaptel crc_ccitt genrtc
CPU: 0
EIP: 0061:[<c01351a7>] Not tainted VLI
EFLAGS: 00010282 (2.6.16.19-xen #1)
EIP is at print_unload_info+0x39/0xf1
eax: 00000000 ebx: fdfefe7f ecx: c035d18d edx: 00001000
esi: c9046a60 edi: c83238c0 ebp: c9046a60 esp: c87e3ef8
ds: 007b es: 007b ss: 0069
Process modprobe (pid: 885, threadinfo=c87e2000 task=c11f6030)
Stack: <0>c83238c0 c035d189 0003ffff 00000000 c9046a64 c9046a60
c83238c0
00000400
c0137777 c83238c0 c9046a60 c9046a6c 00037064 c9046a64 c83238c0
c9046a64
c017d1a3 c83238c0 c9046a64 c848fa34 00000000 c87e2000 00000022
00000000
Call Trace:
[<c0137777>] m_show+0x44/0xa8
[<c017d1a3>] seq_read+0xe1/0x2b8
[<c015d1fa>] vfs_read+0xa4/0x16f
[<c015d598>] sys_read+0x51/0x80
[<c0104d15>] syscall_call+0x7/0xb
Code: 24 c7 44 24 0c 00 00 00 00 89 2c 24 e8 d7 fd ff ff 89 3c 24 89 44
24 08 c7 44 24 04 89 d1 35 c0 e8 85 85 04 00 8b 9d 00 05 00 00 <8b> 03
0f 18 00 90 8d b5 00 05 00 00 39 f3 74 2e c7 44 24 0c 01
/etc/rc2.d/S15zaptel: line 136: 885 Segmentation fault modprobe
ztdummy
<6>Registered tone zone 0 (United States / North America)
zaptel.
-------------------
I've read somewhere that is possible to disable rtc un in ztdummy (
#Define USE_RTC)
http://lists.xensource.com/archives/html/xen-devel/2006-05/msg00962.html
Does anyone have experience or solution to this problem ?
Regards
Sebastien
Duncan Gibb a écrit :
On Sun, 2006-08-13 at 23:56, Jason wrote:
J> thought I would post how I got asterisk playing well
J> in a DomU with an X100P FXO card.
Good to know someone else is also playing with this. Could you post a
bit more detail about when your Xen snapshot was taken, the config
options and the hardware you're using, please?
I have a 600MHz P-III system on which I want to use a Xen domU to
develop zaptel modules without worrying about bringing down the
machine
when I get it wrong.
Using Xen 3.0.2-2 and the standard 2.6.16-xen kernel lightly
reconfigured (1000Hz, serial enabled) almost worked, but the jitter
was
so bad voicemails were incomprehensible (even when left by SIP).
Dialling out on an analogue line with a clone wcfxo card worked only
intermittently because the DTMF synthesis broke up towards the end
of a
10-digit UK number.
CPU load didn't seem to be the problem, and Googling around
suggested a
working RTC might help. I have therefore rebuilt with the Xen nightly
snapshot from Sunday and 2.6.16.13-xen. I'm not convinced that the
RTC
does actually work (still get IRQ 8 not free sometimes), and wcfxo
frequently reports it can't init the DAA (ie interrupts are
probably not
working in the domU).
I've tried both passthrough and vpci pci backend drivers. And I've
turned on permissive mode after seeing warnings when doing modprobe
wcfxo in the domU.
J> The first thing I did was to give up trying to get the zaptel
J> modules to compile in a DomU. I never did get that part working.
My solution to this was to copy the linux build tree from the dom0
over
to /usr/src in the domU, along with the xen tree and the
linux-2.6-xen-sparse tree and symlinking as you did.
Cheers
Duncan
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
Home