Virtualize elastix on OpenVZ?

galaxy

Joined
Jun 22, 2010
Messages
42
Likes
0
Points
0
#1
Is it possible to virtualize Elastix in an OpenVZ container if you have FXO modules? I wouldn't mind installing the zaptel drivers on the hardware node and installing the kernel module on the hardware node. But I'm wondering if anyone else has done this before.

This way I can install the current stable version in one container and the beta version in another and swap back and forth.
 

comedit

Joined
Jun 23, 2010
Messages
1
Likes
0
Points
0
#2
Galaxy,

I have not tried this but this tutorial should probably help:

http://www.howtoforge.com/how-to-conver ... ebian-etch

The elastix is a centos 5.3 I believe so you should alter this indicating the distribution for openvz

Let me know if it works.

I myself run promox (openvz combined with KVM) and chose to run elastix on KVM to make live easier. However the performance of elastix on openvz should be better since it is container virtualization
 

galaxy

Joined
Jun 22, 2010
Messages
42
Likes
0
Points
0
#3
I have the VM set up already. I've been using OpenVZ for years.

The problem is the dahdi drivers, which I've compiled and installed on the HW node.

I noticed in the old original dedicated node the messages had:

Jun 14 20:09:45 elastix kernel: dahdi: Telephony Interface Registered on major 196
Jun 14 20:09:45 elastix kernel: dahdi: Version: 2.2.0.2
Jun 14 20:09:45 elastix kernel: GSI 20 sharing vector 0xC9 and IRQ 20
Jun 14 20:09:45 elastix kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 201
Jun 14 20:09:46 elastix kernel: Freshmaker version: 73
Jun 14 20:09:46 elastix kernel: Freshmaker passed register test
Jun 14 20:09:46 elastix kernel: Module 0: Installed -- AUTO FXO (FCC mode)
Jun 14 20:09:46 elastix kernel: Module 1: Installed -- AUTO FXO (FCC mode)
Jun 14 20:09:46 elastix kernel: Module 2: Installed -- AUTO FXO (FCC mode)
Jun 14 20:09:46 elastix kernel: Module 3: Installed -- AUTO FXO (FCC mode)
Jun 14 20:09:46 elastix kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)
Jun 14 20:09:46 elastix kernel: dahdi_transcode: Loaded.
Jun 14 20:09:47 elastix kernel: INFO-xpp: revision trunk-r6963 MAX_XPDS=64 (8*8)
Jun 14 20:09:47 elastix kernel: INFO-xpp: FEATURE: with BRISTUFF support
Jun 14 20:09:47 elastix kernel: INFO-xpp: FEATURE: with PROTOCOL_DEBUG
Jun 14 20:09:47 elastix kernel: INFO-xpp: FEATURE: with sync_tick() from DAHDI
Jun 14 20:09:47 elastix kernel: INFO-xpp_usb: revision trunk-r6963
Jun 14 20:09:47 elastix kernel: usbcore: registered new driver xpp_usb
Jun 14 20:09:47 elastix kernel: Unified AP4XX PCI Card Driver
Jun 14 20:09:47 elastix kernel: DAHDI Dynamic Span support LOADED
Jun 14 20:09:47 elastix kernel: rxt1: no version for "dahdi_hdlc_putbuf" found: kernel tainted.
Jun 14 20:09:47 elastix kernel: dahdi: Registered tone zone 0 (United States / North America)
Jun 14 20:09:48 elastix kernel: All TDMoE multiframe span groups are active.


However now on the HW node, I see:

Jun 22 20:42:47 sempy kernel: dahdi: Telephony Interface Registered on major 196
Jun 22 20:42:47 sempy kernel: dahdi: Version: 2.3.0.1
Jun 22 20:42:48 sempy kernel: GSI 20 sharing vector 0xC9 and IRQ 20
Jun 22 20:42:48 sempy kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 201
Jun 22 20:42:49 sempy kernel: Freshmaker version: 73
Jun 22 20:42:49 sempy kernel: Freshmaker passed register test
Jun 22 20:42:49 sempy kernel: Module 0: Installed -- AUTO FXO (FCC mode)
Jun 22 20:42:49 sempy kernel: Module 1: Installed -- AUTO FXO (FCC mode)
Jun 22 20:42:49 sempy kernel: Module 2: Installed -- AUTO FXO (FCC mode)
Jun 22 20:42:49 sempy kernel: Module 3: Installed -- AUTO FXO (FCC mode)
Jun 22 20:42:49 sempy kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)
Jun 22 20:42:49 sempy kernel: dahdi_transcode: Loaded.
Jun 22 20:42:49 sempy kernel: INFO-xpp: revision Unknown MAX_XPDS=64 (8*8)
Jun 22 20:42:49 sempy kernel: INFO-xpp: FEATURE: without BRISTUFF support
Jun 22 20:42:49 sempy kernel: INFO-xpp: FEATURE: with PROTOCOL_DEBUG
Jun 22 20:42:49 sempy kernel: INFO-xpp: FEATURE: with sync_tick() from DAHDI
Jun 22 20:42:49 sempy kernel: INFO-xpp_usb: revision Unknown
Jun 22 20:42:49 sempy kernel: usbcore: registered new driver xpp_usb
Jun 22 20:42:50 sempy kernel: dahdi: Registered tone zone 0 (United States / North America)


So the INFO-xpp: lines are different and isn't registering.
 

galaxy

Joined
Jun 22, 2010
Messages
42
Likes
0
Points
0
#4
Well I think I understand the problem with getting a TDM400P card recognized within a VE.

The tools within the VE do recognize the card is there and can access the devices, however the /proc file system in the hardware node contains the /proc/dahdi/1 entry where it can get/set status and is not accessible to the VE.

So until either OpenVZ allows you to map /proc/dahdi to a VE or the DAHDI developers restrict the tools to only use devices in the /dev tree to get/set status (and remove the /proc/dahdi nodes) I don't think it will be possible to delegate cards to VE's.

So you can only use a VE (or container if you prefer) if you do not rely on the PCI cards.
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,901
Messages
130,885
Members
17,561
Latest member
marouen
Top