[asterisk-users] DAHDI on VMWARE

[Danny Nicholas]

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Shaun Ruffell
Sent: Friday, December 03, 2010 9:54 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] DAHDI on VMWARE

On 12/03/2010 08:46 AM, Danny Nicholas wrote:
>> Actually I think I wasn't clear.  Instead of the "latest version of
>> DAHDI-linux" I think I should have said "to the current trunk of
>> dahdi-linux"  i.e.
>> 
>> ]# svn co http://svn.asterisk.org/svn/dahdi/linux/trunk dahdi-linux-trunk
>> ]# cd dahdi-linux-trunk
>> ]# make install
>> ]# /etc/init.d/dahdi stop
>> ]# dmesg -c > /dev/null
>> ]# modprobe wctdm24xxp debug=1
>> ]# dmesg | tee output.txt
>> 
>> The results of output.txt is what I am interested in. 

> Thanks, Shaun
> Output.txt
> [226640.316796] dahdi: Telephony Interface Registered on major 196
> [226640.316797] dahdi: Version: SVN-trunk-r9503
> [226640.321586] wctdm24xxp 0000:13:00.0: PCI INT A -> GSI 16 (level, low)
->
> IRQ 16
> [226640.321604] wctdm24xxp 0000:13:00.0: IO Registers are in use by
another
> module.
> [226640.421189] wctdm24xxp 0000:13:00.0: Did not come out of reset within
> 100ms
> [226640.421191] wctdm24xxp 0000:13:00.0: Failed reset.
> [226640.421222] wctdm24xxp 0000:13:00.0: PCI INT A disabled
> [226640.421227] wctdm24xxp: probe of 0000:13:00.0 failed with error -5
> 
> 

Typically when I see those errors it's because the memory cycles aren't
completing.  I'm not a VMWARE passthrough user/expert (but am interested
if this configuration will work), so I'm not sure if there is an extra
step you need to do to make sure that the memory window is opened up and
whether your host machine must have an IOMMU in order to remap any IO /
DMA transactions.

Do you know whether VMWARE says pci passthrough should work on your host
system?  Have you been able to put a NIC card into the host and setup
PCI-passthrough on it?

My System guy is applying the ESXi4000 U1 patch.  Will let you know if that
fixes it.