On Fri, Jul 8, 2011 at 8:12 PM, Doug Lytle <[email protected]> wrote:
> Patrick Lists wrote: > >> With virtualized environments prone to timing issues does this make sense >> at all? >> > > Wouldn't the timing be taken from the PCI device? This is how it's working > on my systems now. Also, it's not something I would be put into production > until I've hammered it. > > > Doug > > > -- > Ben Franklin quote: > > "Those who would give up Essential Liberty to purchase a little Temporary > Safety, deserve neither Liberty nor Safety." > > Hammer it. Setup whatever requires the most timing, IAX, MOH, conference bridge or whatever. Setup SIPp (http://sipp.sourceforge.net/) to initiate x calls for the duration and then you call in and see where it breaks. Just to test the timing. Piggy back a couple of quad pri systems and have them call each other and SIPp into whatever app is most sensitive to timing. what does cat /proc/interrupts show? This is cool stuff, I will lab it up when I get some spare cycles. I wonder what happens with multiple VMs running Asterisk, I guess only one gets access to the card, or it would be a mess. Doesn't someone make a USB dongle for timing in VMs? Anyone have input on the best way get timing to multiple VMs. I think it is time to start playing with Asterisk in various VM platforms and configurations. I want a stock underlying OS and stock guest OSes. Xorcom has that USB FXX device. Maybe a few of those, or multiple dongles. Multiple FXX PCI cards with no modules assigned to different VMs? Thanks, Steve Totaro
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
