WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Missed interrupt. Increasing latency to 5 ms in orderto

To: "'C. Mylonas \(Mr VoIP\)'" <chris@xxxxxxxxxxxxx>
Subject: RE: [Xen-users] Missed interrupt. Increasing latency to 5 ms in orderto compensate.
From: "Jamie J. Begin" <begin@xxxxxxxxxxxxxxx>
Date: Wed, 11 Jun 2008 02:15:31 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Jun 2008 23:18:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <a4fd8f210806102257r7708dac3r9fbc82374ee1152c@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjLiBd7ypLzFGFSSneV/myIykGSXAAAfFtA
Yes, it's a possibility that I have reluctantly considered.  My reason for
virtualizing it is primarily because the hardware is going to be so
underutilized as simply a VoIP server--and I seem to have come so close to
making it work properly. :-\

But as you correctly guessed, I am walking a management tightrope here with
this project.  It may just not be worth it.

Thanks for the input.

> -----Original Message-----
> From: C. Mylonas (Mr VoIP) [mailto:chris@xxxxxxxxxxxxx]
> Sent: Wednesday, June 11, 2008 1:58 AM
> To: Jamie J. Begin
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Missed interrupt. Increasing latency to 5 ms in
> orderto compensate.
> 
> Dear Jamie,
> 
> I would not be putting telephony onto virtual infrastructure in a
> production environment period.
> If you are looking after this system, and are able to put it back onto a
> physical server, it's not worth the stress of it, especially when using
> the switching network through telephony interface cards.
> 
> As soon as your system chokes, you'll have XX amount of users hurling
> abuse at the phones or yourself, and management will look badly on the
> whole virtualisation thing you're trying to achieve with Xen.
> 
> Chris
> 
> 
> On Wed, Jun 11, 2008 at 12:32 PM, [STD]Ein <ein@xxxxxxxxxxxxxx> wrote:
> 
> 
>       Is it possible the cpu(s) are being taxed?  If they are under heavy
> load (from another domain most likely) it may cause the domain to not
> respond to interrupts in a timely manner.  If this is the case, you might
> try changing the scheduling weights of your domains (search the list).
> 
> 
> 
> 
> ________________________________
> 
> 
>       From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jamie J. Begin
>       Sent: June 10, 2008 1:12 PM
>       To: xen-users@xxxxxxxxxxxxxxxxxxx
>       Subject: [Xen-users] Missed interrupt. Increasing latency to 5 ms in
> orderto compensate.
> 
> 
> 
>       I am using pciback to pass a Digium PCIX analog telephony card to an
> Asterisk domU.  Seemingly at random times, the card wigs out with the
> following appended to my /var/log/messages:
> 
> 
> 
>       Jun 10 12:17:19 asterisk01 kernel: wctdm24xxp0: Missed interrupt.
> Increasing latency to 4 ms in order to compensate.
> 
>       Jun 10 14:01:01 asterisk01 kernel: wctdm24xxp0: Missed interrupt.
> Increasing latency to 5 ms in order to compensate.
> 
> 
> 
>       This is becoming a major problem because it will drop any active
> calls and refuse to accept new calls until I stop Asterisk, remove and
> then re-add the kernel module, and finally restart Asterisk.  I don't know
> whether the drivers, Xen, the motherboard/BIOS, or Asterisk is to blame.
> However, this did not occur until after I virtualized the server.  Does
> anyone have any suggestions?  This is killing me here.
> 
> 
>       _______________________________________________
>       Xen-users mailing list
>       Xen-users@xxxxxxxxxxxxxxxxxxx
>       http://lists.xensource.com/xen-users
> 
> 
> 
> 
> 
> --
> Kind Regards,
> Chris Mylonas
> Engineer


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users