To get MeetMe working properly, I know some sort of timing device provided by the zaptel package is required (even if it means the zt_dummy). But, on a virtual machine I know that the Linux timing won't work as expected. Is it possible to then dedicate a physical device like a USB port or something to the virtual machine to use for the timing interrupts? Thanks.
On Fri, Feb 19, 2010 at 11:42 AM, Mike A. Leonetti <mleonetti at evolutionce.com> wrote:> To get MeetMe working properly, I know some sort of timing device > provided by the zaptel package is required (even if it means the > zt_dummy). ?But, on a virtual machine I know that the Linux timing won't > work as expected. ?Is it possible to then dedicate a physical device > like a USB port or something to the virtual machine to use for the > timing interrupts?You could always use ConfBridge(), starting in 1.6.2.*, which does not require DAHDI/Zaptel, and therefore doesn't require a timer. Let me be the first to tell you that using a virt for a conferencing solution, especially if you want people to actually use it, sounds like a 'Bad Idea'. You could oversubscribe the resources so you don't starve the virt, but we already have a name or that. It's called not using a virt in the first place.
> To get MeetMe working properly, I know some sort of timing device > provided by the zaptel package is required (even if it means the > zt_dummy). But, on a virtual machine I know that the Linux timing won't > work as expected. Is it possible to then dedicate a physical device > like a USB port or something to the virtual machine to use for the > timing interrupts?The 2.2.1 version of DAHDI using DAHDI dummy seems to be working adequately in a Xen environment on CentOS for me, although I haven't been using MeetMe. Have you run into issues with it specifically? Which version of DAHDI are you using? If there are some issues that you have found I would like to know... Thanks, Sean