(SOLVED) Passthrough Digital Devices Cine S2

[chvb]

Hello together,

 

i want to passthrough a Digital Device Cine S2 Cart to my Windows VM.

I've added the Card in the .xml file.

 

The syslinux.cfg is already changed to:

 

append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream initrd=/bzroot

 

 

The Vm doesn't start:

 

internal error: process exited while connecting to monitor: 2016-05-03T09:07:15.474529Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev0,bus=pci.2,addr=0x3: vfio: failed to set iommu for container: Operation not permitted

2016-05-03T09:07:15.474551Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev0,bus=pci.2,addr=0x3: vfio: failed to setup container for group 14

2016-05-03T09:07:15.474556Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev0,bus=pci.2,addr=0x3: vfio: failed to get group 14

2016-05-03T09:07:15.474564Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev0,bus=pci.2,addr=0x3: Device initialization failed

 

This is the error from log:

 

May  3 11:02:04 NAS kernel: ---[ end trace 357031a9f515e633 ]---

May  3 11:02:04 NAS kernel: ------------[ cut here ]------------

May  3 11:02:04 NAS kernel: WARNING: CPU: 0 PID: 20544 at lib/kobject.c:240 kobject_add_internal+0x209/0x25d()

May  3 11:02:04 NAS kernel: kobject_add_internal failed for ddbridge1 with -EEXIST, don't try to register things with the same name in the same directory.

May  3 11:02:04 NAS kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net vhost macvtap macvlan tun iptable_mangle xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod bonding stv6110x lnbp21 mpt3sas stv090x x86_pkg_temp_thermal coretemp kvm_intel ahci libahci tg3 raid_class ddbridge cxd2099© kvm dvb_core ptp pps_core scsi_transport_sas ipmi_si [last unloaded: md_mod]

May  3 11:02:04 NAS kernel: CPU: 0 PID: 20544 Comm: libvirtd Tainted: G        WC      4.4.6-unRAID #1

May  3 11:02:04 NAS kernel: Hardware name: HP ProLiant ML310e Gen8, BIOS J04 11/09/2013

May  3 11:02:04 NAS kernel: 0000000000000000 ffff8806670d7940 ffffffff81368c9a ffff8806670d7988

May  3 11:02:04 NAS kernel: 00000000000000f0 ffff8806670d7978 ffffffff8104a28a ffffffff8136acb9

May  3 11:02:04 NAS kernel: ffff8800d580f010 00000000ffffffef ffff88080359e420 0000000000000000

May  3 11:02:04 NAS kernel: Call Trace:

May  3 11:02:04 NAS kernel: [<ffffffff81368c9a>] dump_stack+0x61/0x7e

May  3 11:02:04 NAS kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8

May  3 11:02:04 NAS kernel: [<ffffffff8136acb9>] ? kobject_add_internal+0x209/0x25d

May  3 11:02:04 NAS kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b

May  3 11:02:04 NAS kernel: [<ffffffff8115a078>] ? sysfs_warn_dup+0x60/0x67

May  3 11:02:04 NAS kernel: [<ffffffff8136acb9>] kobject_add_internal+0x209/0x25d

May  3 11:02:04 NAS kernel: [<ffffffff8136ada3>] kobject_add+0x96/0xa3

May  3 11:02:04 NAS kernel: [<ffffffff814423c7>] device_add+0x101/0x4fc

May  3 11:02:04 NAS kernel: [<ffffffff810cdb23>] ? kfree_const+0x1b/0x1d

May  3 11:02:04 NAS kernel: [<ffffffff8144293f>] device_create_groups_vargs+0xb0/0xe2

May  3 11:02:04 NAS kernel: [<ffffffff81442982>] device_create_vargs+0x11/0x13

May  3 11:02:04 NAS kernel: [<ffffffff814429b2>] device_create+0x2e/0x36

May  3 11:02:04 NAS kernel: [<ffffffffa02d0ed1>] ddb_probe+0xa6f/0xa9e [ddbridge]

May  3 11:02:04 NAS kernel: [<ffffffff8144c550>] ? rpm_resume+0x8c/0x3f3

May  3 11:02:04 NAS kernel: [<ffffffff81397a10>] local_pci_probe+0x38/0x7b

May  3 11:02:04 NAS kernel: [<ffffffff81397a10>] ? local_pci_probe+0x38/0x7b

May  3 11:02:04 NAS kernel: [<ffffffff813984c0>] pci_device_probe+0xe3/0x111

May  3 11:02:04 NAS kernel: [<ffffffff81444a87>] driver_probe_device+0xf2/0x25d

May  3 11:02:04 NAS kernel: [<ffffffff81444d04>] __device_attach_driver+0x6c/0x73

May  3 11:02:04 NAS kernel: [<ffffffff81444c98>] ? driver_allows_async_probing+0x2c/0x2c

May  3 11:02:04 NAS kernel: [<ffffffff814433a9>] bus_for_each_drv+0x78/0x82

May  3 11:02:04 NAS kernel: [<ffffffff8144490c>] __device_attach+0xa1/0x101

May  3 11:02:04 NAS kernel: [<ffffffff81444977>] device_attach+0xb/0xd

May  3 11:02:04 NAS kernel: [<ffffffff81443998>] bus_rescan_devices_helper+0x30/0x55

May  3 11:02:04 NAS kernel: [<ffffffff81443a3a>] store_drivers_probe+0x34/0x4c

May  3 11:02:04 NAS kernel: [<ffffffff81442fe0>] bus_attr_store+0x20/0x25

May  3 11:02:04 NAS kernel: [<ffffffff81159cc4>] sysfs_kf_write+0x34/0x36

May  3 11:02:04 NAS kernel: [<ffffffff81159143>] kernfs_fop_write+0xe8/0x12b

May  3 11:02:04 NAS kernel: [<ffffffff811098df>] __vfs_write+0x21/0xb9

May  3 11:02:04 NAS kernel: [<ffffffff8111fee1>] ? __alloc_fd+0x150/0x160

May  3 11:02:04 NAS kernel: [<ffffffff8111f9b5>] ? __fget+0x72/0x7e

May  3 11:02:04 NAS kernel: [<ffffffff810773c8>] ? percpu_down_read+0xe/0x37

May  3 11:02:04 NAS kernel: [<ffffffff81109ed9>] vfs_write+0xbc/0x160

May  3 11:02:04 NAS kernel: [<ffffffff8110a626>] SyS_write+0x49/0x84

May  3 11:02:04 NAS kernel: [<ffffffff8161edae>] entry_SYSCALL_64_fastpath+0x12/0x6d

May  3 11:02:04 NAS kernel: ---[ end trace 357031a9f515e634 ]---

 

 

thanks for your help

[meep]

Hi There

 

I have a similar card (Digital Devices Octopus) passed through to a Windows 7 VM and it works fine.

 

I'm at work right now so can't dig up specific config details for you but I did post the relevant section from my VM XML a few weeks ago here;

 

https://lime-technology.com/forum/index.php?topic=33092.msg465832#msg465832

 

I'm not sure how much it would help but let me know if there's anything in particular from my config you'd like me to share?

 

 

 

 

[chvb]

thanks for your answer.

 

i used another solution:

https://lime-technology.com/forum/index.php?topic=48630.0