[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 884401] Re: PCI Passthrough for Digium TCE400P Codec C

From: Thomas Huth
Subject: [Qemu-devel] [Bug 884401] Re: PCI Passthrough for Digium TCE400P Codec Card Not working
Date: Sun, 08 Jan 2017 08:52:40 -0000

According to the comment to Alex, this should have been fixed in newer
versions, so setting status to "Fix Released" now.

** Changed in: qemu
       Status: New => Fix Released

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  PCI Passthrough for Digium TCE400P Codec Card Not working

Status in QEMU:
  Fix Released

Bug description:
  trying to use a Digium TCE400P Codec card on a Virtual instance using
  the following information:

  lspci <enter>

  02:08.0 Ethernet controller: Digium, Inc. Wildcard TCE400P transcoder
  base card (rev 11)

  lspci -n <enter>

  02:08.0 0200: d161:8004 (rev 11)

  virsh nodedev-list | grep pci


  printf %x 02

  printf %x 08

  printf %x 0


  # virsh edit vmanager
  <hostdev mode='subsystem' type='pci' managed='yes'>
        <address domain='0x0000' bus='0x02' slot='0x08' function='0x0'/>

  I have SELINUX disabled at this time.

  virsh start vmanager I get the following error message:

  address@hidden qemu]# virsh start vmanager
  error: Failed to start domain vmanager
  error: internal error Process exited while reading console log output: char 
device redirected to /dev/pts/2
  Unable to assign device: PCI region 1 at address 0xdf1fe000 has size 0x400,  
which is not a multiple of 4K
  qemu-kvm: -device 
pci-assign,host=02:08.0,id=hostdev0,configfd=23,bus=pci.0,addr=0x6: Device 
'pci-assign' could not be initialized

  Version Numbers:

  address@hidden qemu]# yum list | grep qemu
  gpxe-roms-qemu.noarch                  0.9.7-6.3.el6_0.1                
  qemu-img.x86_64                        2:         
  qemu-kvm.x86_64                        2:         
  qemu-kvm-tools.x86_64                  2:         

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]