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] Q: best practice isdn pci card

To: Stephan Seitz <s.seitz@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Q: best practice isdn pci card
From: Christo Buschek <crito@xxxxxxxxxx>
Date: Mon, 11 Jun 2007 09:01:44 +0200
Cc: XEN User - listmembers <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 10 Jun 2007 23:59:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <466C74E4.4090200@xxxxxxxxxxxx>
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>
References: <466C74E4.4090200@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello Stephan.

I use a digium b410p isdn card inside a domU as a dedicated device. I
use pciback.hide statement in grub and export the card to the domU where
I need the isdn card. That works good so far and makes it easier to
manage the specific domU. If you need the isdn card in more then one
domain you could also manage it within a domU and use an internal
network to connect to the daemon (dummy nic in dom and bridge it to
other domU as an internal network ala 10.1.1.0/24). I try not to run any
daemon inside dom0). 

greetinx
christo

On Mon, 2007-06-11 at 00:02 +0200, Stephan Seitz wrote:
> Hi,
> 
> next week I'm going to setup one dedicated server for a customer.
> The setup of the current (physical) machine is:
> 
> ISDN-(rcapid)<--(capi via localhost)->[special isdn transfer software]
> 
> the new setup should be:
> 
> ISDN-(rcapid)<-+-(capi to one domU)->[special isdn soft on one vhost]
>                `-(capi to 2nd domU)->[special isdn soft on 2nd vhost]
> 
> Now my question.
> Should I leave PCI handling completely in dom0 and run the rcapid on
> dom0, or should I setup a third domU with this single pci-devices
> routed to the domU?
> 
> ISDN capi protocol isn't able to produce high-volume i/o (max through-
> put w/ overhead is about 75kbit/s), but on our other xenified hosts,
> we left dom0 for xen-administrative tasks only (as it's suggested).
> 
> 
> Thanks for any suggestions.
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


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

<Prev in Thread] Current Thread [Next in Thread>