assembly: 0.882 graphic: 0.877 socket: 0.869 semantic: 0.866 other: 0.865 network: 0.851 instruction: 0.850 device: 0.832 vnc: 0.769 boot: 0.746 mistranslation: 0.739 KVM: 0.668 PCI Passthrough for Digium TCE400P Codec Card Not working trying to use a Digium TCE400P Codec card on a Virtual instance using the following information: lspci 02:08.0 Ethernet controller: Digium, Inc. Wildcard TCE400P transcoder base card (rev 11) lspci -n 02:08.0 0200: d161:8004 (rev 11) virsh nodedev-list | grep pci pci_0000_02_08_0 printf %x 02 2 printf %x 08 8 printf %x 0 0 bus='0x02' slot='0x08' function='0x0' # virsh edit vmanager
I have SELINUX disabled at this time. virsh start vmanager I get the following error message: [root@twins 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: [root@twins qemu]# yum list | grep qemu gpxe-roms-qemu.noarch 0.9.7-6.3.el6_0.1 @updates qemu-img.x86_64 2:0.12.1.2-2.113.el6_0.8 @updates qemu-kvm.x86_64 2:0.12.1.2-2.113.el6_0.8 @updates qemu-kvm-tools.x86_64 2:0.12.1.2-2.113.el6_0.8 updates Here is what my grub.conf looks like (see the addition of the intel_iommu=on: title CentOS Linux (2.6.32-71.29.1.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=/dev/mapper/vg_twins-lv_root rd_LVM_LV=vg_twins/lv_root rd_LVM_LV=vg_twins/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=128M rhgb quiet intel_iommu=on initrd /initramfs-2.6.32-71.29.1.el6.x86_64.img This is a distro bug, not an upstream bug. The error message indicates the version of qemu-kvm you're using doesn't support sub-4k MMIO BARs. This has already been fixed in RHEL6.1. According to the comment to Alex, this should have been fixed in newer versions, so setting status to "Fix Released" now. Oh, I meant "comment from Alex", not "comment to Alex", sorry!