Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

another plea for help. Passing through NIC to Win7

Featured Replies

So I have a pcie ethernet card stubbed pci-stub.id=10ec:8168 and it appears in my win7 "edit" page. It also appears in its own iommu group 14 under "Tools/system devices". ACS Override is enabled.

 

IOMMU group 13
	00:1f.0 ISA bridge [0601]: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller [8086:2670] (rev 09)
	00:1f.1 IDE interface [0101]: Intel Corporation 631xESB/632xESB IDE Controller [8086:269e] (rev 09)
	00:1f.2 RAID bus controller [0104]: Intel Corporation 631xESB/632xESB SATA RAID Controller [8086:2682] (rev 09)
IOMMU group 14
	80:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
IOMMU group 15
	60:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
	60:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] [1002:aa68]

 

But when I start the VM I get the following errors:

 

WHEN STARTING THE VM

internal error: qemu unexpectedly closed the monitor: 2017-03-01T02:28:37.269821Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to set iommu for container: Operation not permitted
2017-03-01T02:28:37.269871Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to setup container for group 14
2017-03-01T02:28:37.269880Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to get group 14
2017-03-01T02:28:37.269903Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: Device initialization failed

 

and also...

 

LIBVIRT LOG

2017-03-01 02:25:12.132+0000: 4894: info : libvirt version: 2.4.0
2017-03-01 02:25:12.132+0000: 4894: info : hostname: Tower
2017-03-01 02:25:12.132+0000: 4894: warning : qemuDomainObjTaint:3885 : Domain id=1 name='Windows 7' uuid=b7c54489-8fad-9061-2320-4fbb16b7720f is tainted: high-privileges
2017-03-01 02:25:12.132+0000: 4894: warning : qemuDomainObjTaint:3885 : Domain id=1 name='Windows 7' uuid=b7c54489-8fad-9061-2320-4fbb16b7720f is tainted: host-cpu
2017-03-01 02:25:12.297+0000: 4889: error : qemuMonitorIORead:586 : Unable to read from monitor: Connection reset by peer
2017-03-01 02:25:12.297+0000: 4889: error : qemuProcessReportLogError:1809 : internal error: qemu unexpectedly closed the monitor: 2017-03-01T02:25:12.266721Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to set iommu for container: Operation not permitted
2017-03-01T02:25:12.266759Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to setup container for group 14
2017-03-01T02:25:12.266765Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to get group 14
2017-03-01T02:25:12.266785Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: Device initialization failed
2017-03-01 02:28:37.134+0000: 4892: warning : qemuDomainObjTaint:3885 : Domain id=2 name='Windows 7' uuid=b7c54489-8fad-9061-2320-4fbb16b7720f is tainted: high-privileges
2017-03-01 02:28:37.134+0000: 4892: warning : qemuDomainObjTaint:3885 : Domain id=2 name='Windows 7' uuid=b7c54489-8fad-9061-2320-4fbb16b7720f is tainted: host-cpu
2017-03-01 02:28:37.298+0000: 4889: error : qemuMonitorIORead:586 : Unable to read from monitor: Connection reset by peer
2017-03-01 02:28:37.298+0000: 4889: error : qemuProcessReportLogError:1809 : internal error: qemu unexpectedly closed the monitor: 2017-03-01T02:28:37.269821Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to set iommu for container: Operation not permitted
2017-03-01T02:28:37.269871Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to setup container for group 14
2017-03-01T02:28:37.269880Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to get group 14
2017-03-01T02:28:37.269903Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.2,addr=0x4: Device initialization failed
2017-03-01 02:30:24.163+0000: 4890: warning : qemuDomainObjTaint:3885 : Domain id=3 name='Windows 7' uuid=b7c54489-8fad-9061-2320-4fbb16b7720f is tainted: high-privileges
2017-03-01 02:30:24.163+0000: 4890: warning : qemuDomainObjTaint:3885 : Domain id=3 name='Windows 7' uuid=b7c54489-8fad-9061-2320-4fbb16b7720f is tainted: host-cpu
2017-03-01 02:30:24.343+0000: 4889: error : qemuMonitorIORead:586 : Unable to read from monitor: Connection reset by peer
2017-03-01 02:30:24.343+0000: 4889: error : qemuProcessReportLogError:1809 : internal error: qemu unexpectedly closed the monitor: 2017-03-01T02:30:24.312019Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to set iommu for container: Operation not permitted
2017-03-01T02:30:24.312077Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to setup container for group 14
2017-03-01T02:30:24.312085Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 14
2017-03-01T02:30:24.312110Z qemu-system-x86_64: -device vfio-pci,host=80:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

I'm a newbie. I've gotten up to this point only from reading the forums here. Any ideas welcome.

 

Thanks,

 

Bob

 

 

If your system doesn't support interrupt remapping, you can allow unsafe interrupts to occur.

 

You may need to modify the following in syslinux.cfg 

 

append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot
  • Author

Thanks!!!   I'll try that tonight.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.