Hey guys, I have been off list for awhile, but thought I would post how I got asterisk playing well in a DomU with an X100P FXO card. The first thing I did was to give up trying to get the zaptel modules to compile in a DomU. I never did get that part working. Instead, you compile the module in your Dom0, but tell the make program to use the sources for DomU. My xen sources are in /usr/src/xen-unstable.hg/, so the sources for linux-xen0 and linux-xenU are in that sub directory. In order to make the least number of modifications to the zaptel make files, you need to setup a link in /lib/modules/2.6.16-xenU/build to /usr/src/xen-unstable.hg/linux-2.6.16-xenU (or whatever kernel version you are running) ls -l /lib/modules/2.6.16-xenU/build lrwxrwxrwx 1 root root 43 Jul 10 19:50 /lib/modules/2.6.16-xenU/build -> /usr/src/xen-unstable.hg/linux-2.6.16-xenU/ Now, download the zaptel sources into whatever directory you want on your Dom0. The next part couldn''t be easier. Just cd into the zaptel directory and run make KVERS=2.6.16-xenU (or again, whatever kernel version you are using) The modules get made and we are almost done. Their is most likely a cleaner way to do the next part, but it works for me. Still in Dom0, run a make install. This will install the modules into your Dom0, but in /lib/modules/2.6.16-xenU/misc directory. copy that directory over to the same place on your DomU and viola, zaptel in DomU. Don''t forget to export the PCI device to DomU (my X100P shows up as 02:03.0 Communication controller: Motorola: Unknown device 5608) and be very sure that you don''t try to load that module into Dom0 for some reason. I did that and my IRQ rate shot through the roof when my DomU booted and locked the box. After that, installing asterisk is straight from the book inside DomU. I have had no problems with jitter or timing and cpu usage for my home (4 phones, very light use) is almost non existent. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com http://lists.xensource.com/xen-users
Hey there, Im on 3.0-unstable change set Fri Mar 31 00:26:07 2006 +0100 9494:8a8361994904 I did set the timer to 1kHz and Im using pci passthru to my domU. My card is just one of those FXO cards off ebay that can be had for 12 bucks. Hardware wise, Im on a Celeron 2.4ghz with 2 gig of RAM and 6 other VMs running (including MythTV with 3 tuners running pretty much non stop) . I did have some RTC trouble when I first attempted this, but the latest version of the zaptel drivers seemed to clear that up. As for sound and stability, it has been rock solid for me on the PSTN and SIP. I have had some trouble with an IAX tunnel to a IAX/PSTN provider, but that ended up being the providers hardware. I use the asterisk machine everyday, record every call and use it for voicemail on the road. as for CPU time, this VM is almost always at 0.00 load. Memory usage is usually around 64M total out of 256M dedicated to this VM, no swap partition. The one time it seems to flake is when my myth box does commercial flagging on several recordings at once and eats up all of my disk IO. Here are an xm info and my asterisk.conf file for that vm. -->asterisk.conf kernel = "/boot/vmlinuz-2.6.16-xenU" memory = 256 name = "asterisk" pci = [''02:03.0''] vif = [ ''ip=10.0.0.129, vifname=asterisk'' ] disk = [ ''phy:vm-vg/asterisk-lv,hda1,w'' ] root = "/dev/hda1 ro" -->xm info host : hive release : 2.6.16-xen0 version : #13 Sat Apr 29 09:22:22 CDT 2006 machine : i686 nr_cpus : 1 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 2660 hw_caps : bfebfbff:00000000:00000000:00000180:0000441d total_memory : 2048 free_memory : 359 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : Fri Mar 31 00:26:07 2006 +0100 9494:8a8361994904 cc_compiler : gcc version 3.4.3 cc_compile_by : root cc_compile_domain : [unknown] cc_compile_date : Thu Mar 30 22:59:18 CST 2006 Duncan Gibb wrote:> 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@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2006-Aug-17 11:26 UTC
Re: [Xen-users] Xen and Asterisk/Zapata WORKING!!
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@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The zaptel drivers use the zaptel hardware for a timing source, so I haven''t had any RTC troubles in my setup. If you have to have asterisk, you may want to consider buying a cheap FXO card and using it instead of the dummy driver. Sébastien CRAMATTE wrote:> 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@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2006-Aug-17 13:56 UTC
Re: [Xen-users] Xen and Asterisk/Zapata WORKING!!
Jason Clark a écrit :> The zaptel drivers use the zaptel hardware for a timing source, so I > haven''t had any RTC troubles in my setup. If you have to have > asterisk, you may want to consider buying a cheap FXO card and using > it instead of the dummy driver. >I will consider this option ... Thanks a lot It''s possible to use timer of an FXO card accross different domU ?> Sébastien CRAMATTE wrote: >> 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@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >>> >>> >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You have to assign the card to one domain, so I don''t think that would be possible. Sébastien CRAMATTE wrote:> Jason Clark a écrit : >> The zaptel drivers use the zaptel hardware for a timing source, so I >> haven''t had any RTC troubles in my setup. If you have to have >> asterisk, you may want to consider buying a cheap FXO card and using >> it instead of the dummy driver. >> > I will consider this option ... Thanks a lot > It''s possible to use timer of an FXO card accross different domU ? > > >> Sébastien CRAMATTE wrote: >>> 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@lists.xensource.com >>>> http://lists.xensource.com/xen-users >>>> >>>> >>>> >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >>> >> >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2006-Aug-17 14:29 UTC
Re: [Xen-users] Xen and Asterisk/Zapata WORKING!!
Hi, Do you don''t use ztdummy driver isn''t ? Conference module works well ? Have you get the lastest zaptel drivers from svn trunk ? Regards Jason a écrit :> Hey there, Im on 3.0-unstable change set Fri Mar 31 00:26:07 2006 > +0100 9494:8a8361994904 > I did set the timer to 1kHz and Im using pci passthru to my domU. My > card is just one of those FXO cards off ebay that can be had for 12 > bucks. Hardware wise, Im on a Celeron 2.4ghz with 2 gig of RAM and 6 > other VMs running (including MythTV with 3 tuners running pretty much > non stop) . I did have some RTC trouble when I first attempted this, > but the latest version of the zaptel drivers seemed to clear that up. > As for sound and stability, it has been rock solid for me on the PSTN > and SIP. I have had some trouble with an IAX tunnel to a IAX/PSTN > provider, but that ended up being the providers hardware. I use the > asterisk machine everyday, record every call and use it for voicemail > on the road. as for CPU time, this VM is almost always at 0.00 load. > Memory usage is usually around 64M total out of 256M dedicated to this > VM, no swap partition. The one time it seems to flake is when my myth > box does commercial flagging on several recordings at once and eats up > all of my disk IO. > Here are an xm info and my asterisk.conf file for that vm. > > > -->asterisk.conf > kernel = "/boot/vmlinuz-2.6.16-xenU" > memory = 256 > name = "asterisk" > pci = [''02:03.0''] > vif = [ ''ip=10.0.0.129, vifname=asterisk'' ] > disk = [ ''phy:vm-vg/asterisk-lv,hda1,w'' ] > root = "/dev/hda1 ro" > > -->xm info > host : hive > release : 2.6.16-xen0 > version : #13 Sat Apr 29 09:22:22 CDT 2006 > machine : i686 > nr_cpus : 1 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 1 > threads_per_core : 1 > cpu_mhz : 2660 > hw_caps : bfebfbff:00000000:00000000:00000180:0000441d > total_memory : 2048 > free_memory : 359 > xen_major : 3 > xen_minor : 0 > xen_extra : -unstable > xen_caps : xen-3.0-x86_32 > platform_params : virt_start=0xfc000000 > xen_changeset : Fri Mar 31 00:26:07 2006 +0100 9494:8a8361994904 > cc_compiler : gcc version 3.4.3 > cc_compile_by : root > cc_compile_domain : [unknown] > cc_compile_date : Thu Mar 30 22:59:18 CST 2006 > > > Duncan Gibb wrote: >> 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@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I haven''t used the conference module because my asterisk is mostly a glorified answering machine and used to PSTN/IAX/SIP outbound calls. But the FXO card should provide a solid timing interface for you. Im using Zaptel 1.2.7 and Asterisk 1.2.10 . I don''t use the ztdummy module at all, only zaptel and wcfxo. Sébastien CRAMATTE wrote:> Hi, > > Do you don''t use ztdummy driver isn''t ? Conference module works well ? > Have you get the lastest zaptel drivers from svn trunk ? > > Regards > > Jason a écrit : >> Hey there, Im on 3.0-unstable change set Fri Mar 31 00:26:07 2006 >> +0100 9494:8a8361994904 >> I did set the timer to 1kHz and Im using pci passthru to my domU. My >> card is just one of those FXO cards off ebay that can be had for 12 >> bucks. Hardware wise, Im on a Celeron 2.4ghz with 2 gig of RAM and 6 >> other VMs running (including MythTV with 3 tuners running pretty much >> non stop) . I did have some RTC trouble when I first attempted this, >> but the latest version of the zaptel drivers seemed to clear that >> up. As for sound and stability, it has been rock solid for me on the >> PSTN and SIP. I have had some trouble with an IAX tunnel to a >> IAX/PSTN provider, but that ended up being the providers hardware. I >> use the asterisk machine everyday, record every call and use it for >> voicemail on the road. as for CPU time, this VM is almost always at >> 0.00 load. Memory usage is usually around 64M total out of 256M >> dedicated to this VM, no swap partition. The one time it seems to >> flake is when my myth box does commercial flagging on several >> recordings at once and eats up all of my disk IO. >> Here are an xm info and my asterisk.conf file for that vm. >> >> >> -->asterisk.conf >> kernel = "/boot/vmlinuz-2.6.16-xenU" >> memory = 256 >> name = "asterisk" >> pci = [''02:03.0''] >> vif = [ ''ip=10.0.0.129, vifname=asterisk'' ] >> disk = [ ''phy:vm-vg/asterisk-lv,hda1,w'' ] >> root = "/dev/hda1 ro" >> >> -->xm info >> host : hive >> release : 2.6.16-xen0 >> version : #13 Sat Apr 29 09:22:22 CDT 2006 >> machine : i686 >> nr_cpus : 1 >> nr_nodes : 1 >> sockets_per_node : 1 >> cores_per_socket : 1 >> threads_per_core : 1 >> cpu_mhz : 2660 >> hw_caps : bfebfbff:00000000:00000000:00000180:0000441d >> total_memory : 2048 >> free_memory : 359 >> xen_major : 3 >> xen_minor : 0 >> xen_extra : -unstable >> xen_caps : xen-3.0-x86_32 >> platform_params : virt_start=0xfc000000 >> xen_changeset : Fri Mar 31 00:26:07 2006 +0100 >> 9494:8a8361994904 >> cc_compiler : gcc version 3.4.3 >> cc_compile_by : root >> cc_compile_domain : [unknown] >> cc_compile_date : Thu Mar 30 22:59:18 CST 2006 >> >> >> Duncan Gibb wrote: >>> 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@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2006-Aug-17 14:47 UTC
Re: [Xen-users] Xen and Asterisk/Zapata WORKING!!
I require to install various Asterisk on a same Xen host So I need to share timer caps across VMs Jason a écrit :> I haven''t used the conference module because my asterisk is mostly a > glorified answering machine and used to PSTN/IAX/SIP outbound calls. > But the FXO card should provide a solid timing interface for you. Im > using Zaptel 1.2.7 and Asterisk 1.2.10 . I don''t use the ztdummy > module at all, only zaptel and wcfxo. > > Sébastien CRAMATTE wrote: >> Hi, >> >> Do you don''t use ztdummy driver isn''t ? Conference module works well ? >> Have you get the lastest zaptel drivers from svn trunk ? >> >> Regards >> >> Jason a écrit : >>> Hey there, Im on 3.0-unstable change set Fri Mar 31 00:26:07 2006 >>> +0100 9494:8a8361994904 >>> I did set the timer to 1kHz and Im using pci passthru to my domU. My >>> card is just one of those FXO cards off ebay that can be had for 12 >>> bucks. Hardware wise, Im on a Celeron 2.4ghz with 2 gig of RAM and 6 >>> other VMs running (including MythTV with 3 tuners running pretty >>> much non stop) . I did have some RTC trouble when I first attempted >>> this, but the latest version of the zaptel drivers seemed to clear >>> that up. As for sound and stability, it has been rock solid for me >>> on the PSTN and SIP. I have had some trouble with an IAX tunnel to a >>> IAX/PSTN provider, but that ended up being the providers hardware. >>> I use the asterisk machine everyday, record every call and use it >>> for voicemail on the road. as for CPU time, this VM is almost >>> always at 0.00 load. Memory usage is usually around 64M total out of >>> 256M dedicated to this VM, no swap partition. The one time it seems >>> to flake is when my myth box does commercial flagging on several >>> recordings at once and eats up all of my disk IO. >>> Here are an xm info and my asterisk.conf file for that vm. >>> >>> >>> -->asterisk.conf >>> kernel = "/boot/vmlinuz-2.6.16-xenU" >>> memory = 256 >>> name = "asterisk" >>> pci = [''02:03.0''] >>> vif = [ ''ip=10.0.0.129, vifname=asterisk'' ] >>> disk = [ ''phy:vm-vg/asterisk-lv,hda1,w'' ] >>> root = "/dev/hda1 ro" >>> >>> -->xm info >>> host : hive >>> release : 2.6.16-xen0 >>> version : #13 Sat Apr 29 09:22:22 CDT 2006 >>> machine : i686 >>> nr_cpus : 1 >>> nr_nodes : 1 >>> sockets_per_node : 1 >>> cores_per_socket : 1 >>> threads_per_core : 1 >>> cpu_mhz : 2660 >>> hw_caps : bfebfbff:00000000:00000000:00000180:0000441d >>> total_memory : 2048 >>> free_memory : 359 >>> xen_major : 3 >>> xen_minor : 0 >>> xen_extra : -unstable >>> xen_caps : xen-3.0-x86_32 >>> platform_params : virt_start=0xfc000000 >>> xen_changeset : Fri Mar 31 00:26:07 2006 +0100 >>> 9494:8a8361994904 >>> cc_compiler : gcc version 3.4.3 >>> cc_compile_by : root >>> cc_compile_domain : [unknown] >>> cc_compile_date : Thu Mar 30 22:59:18 CST 2006 >>> >>> >>> Duncan Gibb wrote: >>>> 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@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >>> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Kanwar Ranbir Sandhu
2006-Aug-21 06:36 UTC
Re: [Xen-users] Xen and Asterisk/Zapata WORKING!!
On Tue, 2006-15-08 at 22:30 +0100, Duncan Gibb wrote:> 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.I was doing this, too, and successfully. However, I recently moved the dom0 to Fedora Core 5. The asterisk domU is still CentOS 4. Now when I try installing the built modules, I get an error about incompatible versions. I don''t understand the error completely because zaptel was built against the domU kernel. I think the error may be because of the different gcc versions in CentOS 4 and Fedora Core 5. Any guesses? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2142_FC4 i686 GNU/Linux 02:30:57 up 1 day, 20:00, 4 users, load average: 0.20, 0.14, 0.10 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
That would be my guess. I''ve had odd mismatches like that in the past, but it''s been so long I can''t remember what I tracked it down to. Kanwar Ranbir Sandhu wrote:> On Tue, 2006-15-08 at 22:30 +0100, Duncan Gibb wrote: > >> 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. >> > > I was doing this, too, and successfully. However, I recently moved the > dom0 to Fedora Core 5. The asterisk domU is still CentOS 4. Now when I > try installing the built modules, I get an error about incompatible > versions. > > I don''t understand the error completely because zaptel was built against > the domU kernel. I think the error may be because of the different gcc > versions in CentOS 4 and Fedora Core 5. Any guesses? > > Regards, > > Ranbir > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users