[asterisk-bugs] [Asterisk-GUI 0011538]: PCI Frontend not enabled in Xen DomU images

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11538 
====================================================================== 
Reported By:                riddles
Assigned To:                bkruse
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   11538
Category:                   Ztscan/Digital Cards
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-13-2007 11:41 CST
Last Modified:              12-13-2007 11:49 CST
====================================================================== 
Summary:                    PCI Frontend not enabled in Xen DomU images
Description: 
In the current Beta6 Xen DomU image (x86_64), the kernel option
CONFIG_XEN_PCIDEV_FRONTEND is not set, making it impossible to use the
Zaptel hardware under Xen. I'm now using CentOS 5 with Asterisk 1.4 in my
DomU instead of AsteriskNOW and it works just fine.

I've tried recompiling the kernel, but even though kernel:build-tree is
installed, I cannot compile the kernel, as the image does not include the
full source. 

This is a fairly odd omission for a DomU kernel. Can this be added in a
next release?
====================================================================== 

---------------------------------------------------------------------- 
 bkruse - 12-13-07 11:49  
---------------------------------------------------------------------- 
I am not sure exactly what you are asking.

But ztscan just recently got added to the zaptel 1.4 branch, check that
out and see if it works (I would not want to support zaptel hardware
through virtual machiens.) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-13-07 11:49  bkruse         Note Added: 0075346                          
======================================================================