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.
--
Stephan Seitz
Senior System Administrator
*netz-haut* e.K.
multimediale kommunikation
zweierweg 22
97074 würzburg
fon: +49 931 2876247
fax: +49 931 2876248
web: www.netz-haut.de <http://www.netz-haut.de/>
registriergericht: amtsgericht würzburg, hra 5054
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christo Buschek schrieb:> 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).Hello Christo, thank you for your response. As I also don''t want to run application daemons inside dom0, I''ll try a similiar setup with the isdn pci card routed to one domU. If there''ll be any problems (I suspect dropped interrupts on high load), I''ll be back on the list ;) Have a nice Day! Stephan -- Stephan Seitz Senior System Administrator *netz-haut* e.K. multimediale kommunikation zweierweg 22 97074 würzburg fon: +49 931 2876247 fax: +49 931 2876248 web: www.netz-haut.de <http://www.netz-haut.de/> registriergericht: amtsgericht würzburg, hra 5054 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users