[asterisk-bugs] [AsteriskNOW 0011538]: PCI Frontend not enabled in Xen DomU images
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Jan 7 15:18:12 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11538
======================================================================
Reported By: riddles
Assigned To: james
======================================================================
Project: AsteriskNOW
Issue ID: 11538
Category: Card Detection
Reproducibility: always
Severity: feature
Priority: normal
Status: acknowledged
======================================================================
Date Submitted: 12-13-2007 11:41 CST
Last Modified: 01-07-2008 15:18 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 - 01-07-08 15:18
----------------------------------------------------------------------
Oh!
Thats right riddles, my apologies. Xen does have "limited" zaptel
support.
But for what is has so far, I think the config should be switched on to
support what it does.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
01-07-08 15:18 bkruse Note Added: 0076452
======================================================================
More information about the asterisk-bugs
mailing list