March 20, 201610 yr Having trouble passing through a 4port NIC to a VM. Receive a "Requested operation is not valid: PCI device 0000:04:00.0 is not assignable" error when trying to start the VM. stubbed the device using @jonp guide - http://lime-technology.com/forum/index.php?topic=39638.0 04:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 04:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) and have PCIe ACS Override turned on /sys/kernel/iommu_groups/17/devices/0000:04:00.0 /sys/kernel/iommu_groups/17/devices/0000:04:00.1 /sys/kernel/iommu_groups/18/devices/0000:05:00.0 /sys/kernel/iommu_groups/18/devices/0000:05:00.1 also tried adding qemu commands to the XML per this solution - http://lime-technology.com/forum/index.php?topic=44147.0 <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.0,bus=root.1,addr=00.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.1,bus=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=05:00.0,bus=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=05:00.1,bus=root.1'/> </qemu:commandline> Not really sure where to turn to at this point, but any help would be appreciated. EDIT: additional PCI info 04:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f7b20000 (32-bit, non-prefetchable) [size=128K] Memory at f7a80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c020 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-26-55-ff-ff-ec-ab-08 Kernel driver in use: pci-stub Kernel modules: e1000e 04:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at f7b00000 (32-bit, non-prefetchable) [size=128K] Memory at f7a00000 (32-bit, non-prefetchable) [size=512K] I/O ports at c000 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-26-55-ff-ff-ec-ab-08 Kernel driver in use: pci-stub Kernel modules: e1000e 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter Flags: bus master, fast devsel, latency 0, IRQ 3 Memory at f7920000 (32-bit, non-prefetchable) [size=128K] Memory at f7880000 (32-bit, non-prefetchable) [size=512K] I/O ports at b020 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-26-55-ff-ff-ec-ab-0a Kernel driver in use: pci-stub Kernel modules: e1000e 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f7900000 (32-bit, non-prefetchable) [size=128K] Memory at f7800000 (32-bit, non-prefetchable) [size=512K] I/O ports at b000 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-26-55-ff-ff-ec-ab-0a Kernel driver in use: pci-stub Kernel modules: e1000e 07:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7917 Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at f7c00000 (64-bit, non-prefetchable) [size=256K] I/O ports at d000 [size=128] Capabilities: [40] Power Management version 3 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [c0] MSI: Enable+ Count=1/16 Maskable+ 64bit+ Capabilities: [d8] MSI-X: Enable- Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [180] Device Serial Number ff-53-be-f5-d8-cb-8a-ff Kernel driver in use: alx Kernel modules: alx
March 21, 201610 yr Author Thanks, @jonp. This solved the issue. Here you go; Linux 3.19.4-unRAID. root@UnRaid:~# virsh start MediaServer error: Failed to start domain MediaServer error: Requested operation is not valid: PCI device 0000:0e:00.0 is not assignable Ok, let's try this: 1) Stop all your running VMs 2) Login via SSH or telnet 3) type the following command: nano /etc/libvirt/qemu.conf 4) Hit CTRL+W on your keyboard (this searches in nano). Search for the word "relaxed" 5) Uncomment this line: #relaxed_acs_check = 1 6) Hit CTRL+X on your keyboard to exit, when prompted to save modified buffer, hit "y" for yes 7) Exit SSH/telnet Navigate your browser to Settings -> VM Manager 9) Set "Enable VMs" to No and then to Yes again (restarting libvirt) 10) Try to start your VM again...
March 21, 201610 yr Author I might as well use the same thread since my next issue is related. Since I was able to pass through the NIC, I've configured the WAN and LAN on a pfSense VM. However, the issue I'm having is getting unRaid to use the LAN I configured. I have a static IP assigned in unRaid, but that fails to show in pfSense, specifically in the ARP table. I'm guessing it's an unRaid network settings configuration issue? Moreover, I can only access the webgui from inside a Win 10 VM (which also doesn't have internet connection - VirtIO Ethernet adapter shows sent and received activity though) "DNS_PROBE_FINISHED_NO_INTERNET" error from chrome.. EDIT: Attached UnRaid Diagnostics tower-diagnostics-20160322-1024.zip
March 22, 201610 yr Author So I was able to get around this issue by physically connecting ETH0 (the onboard NIC I left open for unRaid - not sure if this was necessary) to my Access Point (old router) which is connected physically to the LAN port on the NIC I passed through to pfSense. Is this the appropriate configuration - using a physical connection? Shouldn't I be able to bridge the LAN to unRaid?
Archived
This topic is now archived and is closed to further replies.