PCI Passthrough Problems

S

shaman01

New Member
Aug 28, 2012
13
0
1
Hi all,
I am running the latest Proxmox, version 3.3-139
I try to passthrough a pci device to my vm:
Code: 
03:00.0 Ethernet controller: Digium, Inc. Wildcard TDM410 4-port analog card (rev 11)        Subsystem: Digium, Inc. Wildcard TDM410 4-port analog card
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at d000 [size=256]
        Region 1: Memory at f7c20000 (32-bit, non-prefetchable) [size=1K]
        Expansion ROM at dfb00000 [disabled] [size=128K]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: pci-stub
I add the hostpci command to my vm:
Code: 
# cat /etc/pve/qemu-server/101.conf
bootdisk: virtio0
cores: 1
ide2: none,media=cdrom
memory: 512
name: pbx
net0: virtio=A6:C9:BC:8B:9F:57,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
virtio0: pve:vm-101-disk-1,size=10G
hostpci0: 03:00.0

But the vm don't start
Code: 
# qm start 101
kvm: -device pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: PCI region 1 at address 0xf7c20000 has size 0x400, which is not a multiple of 4K.  You might experience some performance hit due to that.
kvm: -device pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: Failed to assign irq for "hostpci0"
Perhaps you are assigning a device that shares an IRQ with another device?: Input/output error
kvm: -device pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: Device initialization failed.
kvm: -device pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: Device 'kvm-pci-assign' could not be initialized
start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -name pbx -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -k en-us -m 512 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:61fde84539cb' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/dev/pve/vm-101-disk-1,if=none,id=drive-virtio0,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=A6:C9:BC:8B:9F:5          7,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
Code: 
Jan 11 01:39:56 ixi qm[4120]: <root@pam> starting task UPID:ixi:00001019:000062F1:54B1AA3C:qmstart:101:root@pam:Jan 11 01:39:56 ixi qm[4121]: start VM 101: UPID:ixi:00001019:000062F1:54B1AA3C:qmstart:101:root@pam:
Jan 11 01:39:57 ixi kernel: pci-stub 0000:03:00.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900003)
Jan 11 01:39:57 ixi kernel: device tap101i0 entered promiscuous mode
Jan 11 01:39:57 ixi kernel: vmbr0: port 5(tap101i0) entering forwarding state
Jan 11 01:39:57 ixi kernel: pci-stub 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan 11 01:39:57 ixi kernel: pci-stub 0000:03:00.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900003)
Jan 11 01:39:58 ixi kernel: assign device 0:3:0.0
Jan 11 01:39:58 ixi kernel: IRQ handler type mismatch for IRQ 16
Jan 11 01:39:58 ixi kernel: current handler: ehci_hcd:usb1
Jan 11 01:39:58 ixi kernel: Pid: 4128, comm: kvm veid: 0 Not tainted 2.6.32-34-pve #1
Jan 11 01:39:58 ixi kernel: Call Trace:
Jan 11 01:39:58 ixi kernel: [<ffffffff810f7a27>] ? __setup_irq+0x3e7/0x440
Jan 11 01:39:58 ixi kernel: [<ffffffffa0327c90>] ? kvm_assigned_dev_intr+0x0/0xf0 [kvm]
Jan 11 01:39:58 ixi kernel: [<ffffffff810f7b64>] ? request_threaded_irq+0xe4/0x1e0
Jan 11 01:39:58 ixi kernel: [<ffffffffa032d5cd>] ? kvm_vm_ioctl+0x100d/0x10f0 [kvm]
Jan 11 01:39:58 ixi kernel: [<ffffffff81461491>] ? pci_conf1_read+0xc1/0x120
Jan 11 01:39:58 ixi kernel: [<ffffffff81463203>] ? raw_pci_read+0x23/0x40
Jan 11 01:39:58 ixi kernel: [<ffffffff812ac47a>] ? pci_read_config+0x25a/0x280
Jan 11 01:39:58 ixi kernel: [<ffffffff811bcb9a>] ? vfs_ioctl+0x2a/0xa0
Jan 11 01:39:58 ixi kernel: [<ffffffff8122a886>] ? read+0x166/0x210
Jan 11 01:39:58 ixi kernel: [<ffffffff811bd1ce>] ? do_vfs_ioctl+0x7e/0x5a0
Jan 11 01:39:58 ixi kernel: [<ffffffff811a7156>] ? vfs_read+0x116/0x190
Jan 11 01:39:58 ixi kernel: [<ffffffff811bd73f>] ? sys_ioctl+0x4f/0x80
Jan 11 01:39:58 ixi kernel: [<ffffffff8100b182>] ? system_call_fastpath+0x16/0x1b
Jan 11 01:39:58 ixi kernel: deassign device 0:3:0.0
Jan 11 01:39:58 ixi kernel: pci-stub 0000:03:00.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900003)
Jan 11 01:39:58 ixi kernel: pci-stub 0000:03:00.0: PCI INT A disabled
Jan 11 01:39:58 ixi kernel: vmbr0: port 5(tap101i0) entering disabled state
Jan 11 01:39:58 ixi qm[4121]: start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -name pbx -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -k en-us -m 512 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:61fde84539cb' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/dev/pve/vm-101-disk-1,if=none,id=drive-virtio0,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=A6:C9:BC:8B:9F:57,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
Jan 11 01:39:58 ixi qm[4120]: <root@pam> end task UPID:ixi:00001019:000062F1:54B1AA3C:qmstart:101:root@pam: start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -name pbx -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -k en-us -m 512 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:61fde84539cb' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/dev/pve/vm-101-disk-1,if=none,id=drive-virtio0,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=A6:C9:BC:8B:9F:57,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
Have you any ideas?
I have enabled IOMMU in GRUB
dmesg on the proxmox server:
Code: 
# dmesg | grep -e DMAR -e IOMMU
ACPI: DMAR 00000000d6268ea0 000B8 (v01 INTEL  DQ77MK   0000003A INTL 00000001)
Intel-IOMMU: enabled
dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020e60262 ecap f0101a
dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f0105a
IOMMU 0xfed90000: using Queued invalidation
IOMMU 0xfed91000: using Queued invalidation
IOMMU: Setting RMRR:
IOMMU: Setting identity map for device 0000:00:02.0 [0xd7800000 - 0xdfa00000]
IOMMU: Setting identity map for device 0000:00:1d.0 [0xd61f1000 - 0xd61fe000]
IOMMU: Setting identity map for device 0000:00:1a.0 [0xd61f1000 - 0xd61fe000]
IOMMU: Setting identity map for device 0000:00:14.0 [0xd61f1000 - 0xd61fe000]
IOMMU: Prepare 0-16MiB unity mapping for LPC
IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0x1000000]

Here is my pveversion -v:
Code: 
proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
For PCI Express Pass-through you need the 3.10 Kernel.

 
Kernel 3.10 is stable and required for this feature.
do you have tried it with the 3.10 Kernel?
 
Last edited:
Tried with vfio and 3.10 kernel. Not working :(
Code: 
# qm start 101
kvm: -device vfio-pci,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: vfio: Error: Failed to setup INTx fd: Device or resource busy
kvm: -device vfio-pci,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: Device initialization failed.
kvm: -device vfio-pci,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: Device 'vfio-pci' could not be initialized
start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-serve r/101.pid -daemonize -name pbx -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -k en-us -m 512 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'vfio-pci,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:61fde84539cb' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/dev/pve/vm-101-disk-1,if=none,id=drive-virtio0,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=A6:C9:BC:8B:9F:57,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
Code: 
# qm config 101
bootdisk: virtio0
cores: 1
hostpci0: 03:00.0,driver=vfio
ide2: none,media=cdrom
memory: 512
name: pbx
net0: virtio=A6:C9:BC:8B:9F:57,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
virtio0: pve:vm-101-disk-1,size=10G
Code: 
03:00.0 Ethernet controller: Digium, Inc. Wildcard TDM410 4-port analog card (rev 11)        
        Subsystem: Digium, Inc. Wildcard TDM410 4-port analog card
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at d000 [disabled] [size=256]
        Region 1: Memory at f7c20000 (32-bit, non-prefetchable) [disabled] [size=1K]
        Expansion ROM at f7c00000 [disabled] [size=128K]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: vfio-pci

 
It seems that kvm can't handle IRQ sharing here properly.
Code: 
# cat /proc/interrupts           CPU0       CPU1       CPU2       CPU3
  0:         31          0          0          0  IR-IO-APIC-edge      timer
  8:          1          0          0          0  IR-IO-APIC-edge      rtc0
  9:          0          0          0          0  IR-IO-APIC-fasteoi   acpi
[B] 16:         33          0          0          0  IR-IO-APIC-fasteoi   ehci_hcd:usb1[/B]

dmesg output after starting vm
Code: 
[209822.781517] vfio-pci 0000:03:00.0: enabling device (0000 -> 0003)
[B][209822.804143] genirq: Flags mismatch irq 16. 00000000 (vfio-intx(0000:03:00.0)) vs. 00000080 (ehci_hcd:usb1)[/B]
[209822.804215] CPU: 3 PID: 23337 Comm: kvm Tainted: G           O--------------   3.10.0-6-pve #1
[209822.804216] Hardware name:                  /DQ77MK, BIOS MKQ7710H.86A.0058.2013.0226.1541 02/26/2013
[209822.804218]  ffff880403cba880 ffff880405f8bc58 ffffffff81612508 ffff880405f8bcb8
[209822.804221]  ffffffff810f46af ffff880405f8bcb8 0000000000000246 ffff88040d801900
[209822.804223]  ffff880406130c00 ffff880405f8bd28 ffffffffa06209a0 0000000000000000
[209822.804226] Call Trace:
[209822.804232]  [<ffffffff81612508>] dump_stack+0x19/0x1b
[209822.804235]  [<ffffffff810f46af>] __setup_irq+0x51f/0x550
[209822.804239]  [<ffffffffa06209a0>] ? virqfd_shutdown+0x60/0x60 [vfio_pci]
[209822.804242]  [<ffffffff810f47b7>] request_threaded_irq+0xd7/0x180
[209822.804244]  [<ffffffffa0620c63>] vfio_intx_set_signal+0x113/0x1e0 [vfio_pci]
[209822.804247]  [<ffffffffa0621098>] vfio_pci_set_intx_trigger+0xc8/0x1a0 [vfio_pci]
[209822.804250]  [<ffffffffa06219e1>] vfio_pci_set_irqs_ioctl+0xb1/0xe0 [vfio_pci]
[209822.804253]  [<ffffffff81157cf6>] ? memdup_user+0x46/0x90
[209822.804256]  [<ffffffff8161611d>] ? mutex_lock+0x1d/0x41
[209822.804258]  [<ffffffffa061fea9>] vfio_pci_ioctl+0x329/0x980 [vfio_pci]
[209822.804261]  [<ffffffff8118ed22>] ? kmem_cache_alloc+0x1b2/0x1e0
[209822.804263]  [<ffffffff811ab5ac>] ? get_empty_filp+0x5c/0x1b0
[209822.804266]  [<ffffffffa0622b0f>] ? vfio_basic_config_read+0x3f/0x190 [vfio_pci]
[209822.804270]  [<ffffffff811ea00b>] ? fsnotify+0x24b/0x340
[209822.804273]  [<ffffffff8125c1b6>] ? security_file_alloc+0x16/0x20
[209822.804276]  [<ffffffff811c7e12>] ? mnt_clone_write+0x12/0x30
[209822.804279]  [<ffffffffa0613063>] vfio_device_fops_unl_ioctl+0x23/0x30 [vfio]
[209822.804282]  [<ffffffff811bc2d0>] do_vfs_ioctl+0x90/0x530
[209822.804285]  [<ffffffff811a9e50>] ? vfs_write+0x170/0x1f0
[209822.804287]  [<ffffffff811bc801>] SyS_ioctl+0x91/0xb0
[209822.804289]  [<ffffffff811aa2ab>] ? SyS_write+0x6b/0xa0
[209822.804293]  [<ffffffff81622619>] system_call_fastpath+0x16/0x1b

IRQ 16 is used by ehci_hcd:usb1

Has anyone come across this issue before? Thanks.
Code: 
# lspci -vt-[0000:00]-+-00.0  Intel Corporation 2nd Generation Core Processor Family DRAM Controller
           +-02.0  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller
           +-14.0  Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
           +-16.0  Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1
           +-16.3  Intel Corporation 7 Series/C210 Series Chipset Family KT Controller
           +-19.0  Intel Corporation 82579LM Gigabit Network Connection
           +-1a.0  Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2
           +-1b.0  Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller
           +-1c.0-[01]--
           +-1c.6-[02]----00.0  Intel Corporation 82574L Gigabit Network Connection
           +-1d.0  Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1
[B]           +-1e.0-[03]----00.0  Digium, Inc. Wildcard TDM410 4-port analog card[/B]
           +-1f.0  Intel Corporation Q77 Express Chipset LPC Controller
           +-1f.2  Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
           \-1f.3  Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller
 
although this is quite old, I'll try to add my inputs with this.

I have a similar problem with this passing a PCI card (dual intel nic) unto 2 different processor/motherboard combo:

1st group: intel xeon e5520 + intel dx58so
2nd group: intel xeon e3-1220l + asrock p67 extreme4

as far as I have noticed on this one with PCI passthrough devices, IT WILL WORK "IF" all usb is/are disabled.

all hardware configurations are tested with proxmox 4.1 and on gentoo linux

notes:
-- pci give a lot of headaches if to be passthrough :( :)
-- stay away from pci devices if to be passthrough..., use pci-e instead
-- if cant passthrough (nic/digium/etc) use virtio/ovs/etc combo.
 
Hello !
Sorry for my English with failures, but, kindly, a good friend can help me. I recently installed proxmox and together I installed the voip elastik system with the TDM800p digium card. The elastik did not recognize the board is it possible to do this process by proxmox for the elastik to hear tdm800p board? If someone has done this feat could give me a rescue ..
 
marcospupo said:
Hello !
Sorry for my English with failures, but, kindly, a good friend can help me. I recently installed proxmox and together I installed the voip elastik system with the TDM800p digium card. The elastik did not recognize the board is it possible to do this process by proxmox for the elastik to hear tdm800p board? If someone has done this feat could give me a rescue ..
Click to expand...

Hi Marco, you can solve this problem?

Im have this problem in the moment and try all to solve but dont have good news.

If you solve please help me.

Thanks!
 
  • Like
Reactions: admoin
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back