bungee91

While there are certainly more, this should be helpful (scroll down a little) http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Lime_Technology_Tested_Components Also, this is helpful (also in the wiki) https://docs.google.com/spreadsheets/d/1LnGpTrXalwGVNy0PWJDURhyxa3sgqkGXmvNCIvIMenk/edit#gid=0

I'll attempt some of the tips, and I've definitely looked through the wiki prior to now. Not saying it'd be identical by any means, however you've noted success with a 5450, so I wouldn't think it'd be that difficult to achieve. Mine for whatever reason identifies as a 5430, however it's within the same family of GPU so I doubt it matters much. Complete lockup plus parity check is no fun to do repeatedly!

Will give it a shot, thanks for the feedback today!. I would think this would be more helpful for reboots than complete off/on conditions, however will certainly try it out.

So I thought, what the hell, lets try out passing a GPU again, as previously (around beta 9 or so) I had issues, and other annoyances, enough to just give up (others have shared these experiences). So anyhow I have 2 GPU's that I could pass, an AMD 5450, and an Nvidia GeForce210. I have a Windows 8.1 x64 Pro VM that works very well, has a tuner and NIC passed through, I use VNC and RDP to access (I have some small issues with the tuner, but not a show stopper). Shutdown that VM and plan to use it's existing installed image for trying out GPU pass-through. I also completely power off/on (as I am still passing the tuner and NIC in all these GPU passing attempts, and I have to do that for the tuner if I completely shutdown the VM). I create a new VM using the vm manager, point it to W8.1 existing installed image, i440fx-2.3, SeaBios, assign the HD5450, manually add back in tuner and NIC, and we're booting up things are working well. My console screen is now locked up (known issue with SeaBios and pass through, no biggie). Install Catayst drivers, needs to reboot.....nope...server locked up, no network access, console (as mentioned) is dead... Hard shutdown.. Ok, it happens, let's try now with the Geforce 210. New VM setup, point to w8.1x64 existing installed image, Hyper V is turned off (I used the VM manager, does it automatically) install Nvidia drivers... During this time Windows has already given it some driver automatically, no biggie.. Nvidia install completes, I hear an eject sound, look in device manager, something like "driver for device stopped etc..." yellow exclamation, screen is still outputting at 1080p. Either way, need to reboot....same....nothing, black screen... locked up...hard reboot... You could ask for logs, etc... it would likely have nothing as the hard lock-up isn't going to have it write much. I can pass through a NIC, tuner, USB devices, etc... with minimal issues. GPU's work, however without being able to reboot and it causing the server to completely lock (or so it seems, I have no way of accessing it) it is in turn a failure, and unusable. So, I have to know, are people passing through GPU's, and it works well enough (like you can reboot)? Maybe these cards just suck, IDK, they are low power, and IMHO perfect for this use-case (basic video out with HDMI for HTPC uses). I could attempt OVMF, however I would need to do a complete new install of 8.1, and as of now I don't want to attempt that. Just thought "hey, would be cool to shut down that dedicated HTPC now that my server does my tuner recording, that'd be awesome..." Nope. Bios is as new as it gets, MB is AsRock Z97-Extreme4, nothing else special going on... Some info on the AMD setup (GPU+Audio): 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 5450] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0000000 (64-bit, prefetchable) [disabled] [size=256M] Region 2: Memory at f7020000 (64-bit, non-prefetchable) [disabled] [size=128K] Region 4: I/O ports at e000 [disabled] [size=256] Expansion ROM at f7000000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] Subsystem: ASUSTeK Computer Inc. Device aa68 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 10 Region 0: Memory at f7040000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Geforce (GPU+Audio): 02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device 1160 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 10 Region 0: Memory at f5000000 (32-bit, non-prefetchable) [disabled] [size=16M] Region 1: Memory at c0000000 (64-bit, prefetchable) [disabled] [size=256M] Region 3: Memory at d0000000 (64-bit, prefetchable) [disabled] [size=32M] Region 5: I/O ports at d000 [disabled] [size=128] Expansion ROM at f6000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [78] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <1us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting <?> Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> 02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) Subsystem: ZOTAC International (MCO) Ltd. Device 1160 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 5 Region 0: Memory at f6080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [78] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <1us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Should I attempt to load the gpu rom file within the xml? Or look to see if there is any type of firmware update available that may help?

I was going to post the same assumption. Have you tried adding the vfio-bind command to unRAID's "go" file so that the tv tuner isn't seen by unRAID? I doubt this would fix it but it is certainly worth trying. Should add something like this to your "go" file but change the "0000:01:00.0" to match your tv tuner's ID -> toolts -> system devices I can try it, I do like how the VM manager (however it does it) automatically binds it for you now, however if it is causing an issue it is dead to me!.. I could stub it so that unRaid really doesn't see it, however it shouldn't bind this type of adapter regardless (certainly had to do that with the NIC, which as mentioned works very well). I know in the XEN days (here, not in general) that with GPU pass you could eject it prior to shutdown, which would help this kind of situation, however that was specific to GPU's, and no clue if it is even helpful under KVM.

I have a tuner card passed into a W8.1 VM that works very well when it is available within the VM. From a complete off state, power on my server, load VM, all is well! I can reboot the VM, and all is well. I cannot shutdown the VM and power it back up, that specific device will not show up in the device manager of the VM. I do not receive any errors from starting the VM, such as device not available, etc... I do believe I have seen an error message before if I edit the VM and then try to start it (when the device is at that point in this odd state). The only thing I can do to fix it (reset it) is a complete power down of the server, drain the power (switch off supply), wait, boot up. So, the device is likely hanging on once the VM shuts down, and will not reset when it comes back up. I assume this is an issue as the device does not support FLReset (function level reset) and I just have to live with it.... However neither does the NIC that I am passing through,and works every time! Device info on the tuner card in question: 06:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 01) Subsystem: Avermedia Technologies Inc Device 1e55 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f6e00000 (64-bit, non-prefetchable) [size=1M] Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [50] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [74] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] Vendor Specific Information: Len=50 <?> Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=088 <?> Kernel driver in use: vfio-pci Device info on the NIC I pass which works great!: 09:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Intel Corporation PRO/1000 PT Server Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 48 Region 0: Memory at f6b40000 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f6b20000 (32-bit, non-prefetchable) [size=128K] Region 2: I/O ports at 9000 [disabled] [size=32] Expansion ROM at f6b00000 [disabled] [size=128K] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee00618 Data: 0000 Capabilities: [e0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [140 v1] Device Serial Number 00-15-17-ff-ff-c0-48-03 Kernel driver in use: vfio-pci Kernel modules: e1000e I do see the NIC has a "Kernel modules: e1000e" listed where the tuner does not.. Maybe there is just that much better support for the NIC that it works well?.. If there is anything I can force in the XML for this to reset, that'd be fantastic.

Got that (3 posts above), how's it looking?.. I think he's talking to you (Homer Simpson reference!).. Yes and no, however sorry to hear your having the issue also! The difference is I have an Intel NIC as my main adapter, and had the similar issue to you. I never tried a video with RDP, however it is likely the same kind of traffic/situation that is causing it. However, passing through a physical $10 used Intel NIC has solved this issue for me entirely (also read, not using netkvm whatsoever in this VM). Now it would be nice to have netkvm have a NIC for transfers to the array, as I am now going through a physical NIC, down the wire, and back into the server for transfers from downloaded torrents, etc... However, 1Gbps LAN is faster than my image of a HDD that I use for storing/downloading files, so other than it not being the "right way" to do it, it works, and it works well. So unless I am feeling like dealing with the issues OR there is a fix specific to this, for now I am all set with physically passing a separate NIC to this particular VM.

Just to rule it out (I've had to do this prior multiple times), did you try completely powering down, removing power, hitting the power button (to drain residual power), waiting like 10 seconds, then powering back on?.. I've had both my tuner and my GPU lock into a state that only a complete drained power cycle would fix.

Thought of one more thing I want to make sure to point out, in case it is causing issues. In the VM for the NIC (virtio in this case) I force the IP in W8 at the adapter (TCP/IPv4 only, I never touch v6) to a static address, define the gateway, and add in DNS (it makes you define the DNS when you force the address) to 8.8.8.8 & [glow=red,2,300]4.4.8.8[/glow] (which I now no is absolutely incorrect, and I have those #'s wrong should be "8.8.4.4", however I wouldn't think the alternate DNS being wrong would cause a major issue). Anyhow, in case this could cause an issue with assignment, etc... thought I'd mention. It does not cause any issues as I explained the use case in the previous post. I think I was just being lazy at the time, so I will set the static address in the router, and set that back to DHCP.

Ok, we need to get a full diagnostic and then I need to know how you do your networking (both physical and logical). Get me as much info as you can. I'd love the help, can you tell me the commands that would be best to provide the requested information? Edit: I'll just start spit balling here, and you can tell me what's relevant and what I missed... I have a network bridge enabled, br0, under network settings, DHCP enabled, Enable STP-Yes, No bonding. Intel Onboard NIC is the main one (Giga PHY Intel® I218V), used for everything. Gigabit, Cat5e/6, nothing special here.... I had lockup issues prior to the new NIC (identical issues), but now that I have it I will explain. The VM is solid without me trying to access it from other clients/connections (so it doing connecting to the outside world (torrents, RSS) all work without issue). acs downstream enabled (have to), have the new NIC stubbed, and passed to the VM. I originally had the settings for this <interface type='bridge'> <mac address='52:54:00:81:17:c1'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> and then with my new NIC I added this <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> Nothing too fancy in the VM, virtio netkvm stable, have tried the 105 release (which was the newest), didn't mess with the 100 that was mentioned here. Streaming things from the VM to other clients just has issues, brings down the bridge and connection all together, I used to just restart from the console (using powerdown), however now I can just pull the cable, and it fixes it. Here is what ifconfig shows me right now br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.161 netmask 255.255.255.0 broadcast 192.168.1.255 ether d0:50:99:28:ee:69 txqueuelen 0 (Ethernet) RX packets 1719689 bytes 138009172 (131.6 MiB) RX errors 0 dropped 36611 overruns 0 frame 0 TX packets 808691 bytes 10342825779 (9.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 26:e7:96:be:9c:3a txqueuelen 0 (Ethernet) RX packets 129235 bytes 460164706 (438.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 204363 bytes 23840332 (22.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:50:99:28:ee:69 txqueuelen 1000 (Ethernet) RX packets 3082672 bytes 953383491 (909.2 MiB) RX errors 0 dropped 42 overruns 0 frame 0 TX packets 9789739 bytes 12941788609 (12.0 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7100000-f7120000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 6672 bytes 723257 (706.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6672 bytes 723257 (706.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth00b4144: flags=67<UP,BROADCAST,RUNNING> mtu 1500 ether d2:bf:e2:5d:d2:53 txqueuelen 0 (Ethernet) RX packets 16 bytes 2012 (1.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 212 bytes 25614 (25.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth32be0fc: flags=67<UP,BROADCAST,RUNNING> mtu 1500 ether 26:e7:96:be:9c:3a txqueuelen 0 (Ethernet) RX packets 2967 bytes 1566266 (1.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4042 bytes 5358481 (5.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethae38e7a: flags=67<UP,BROADCAST,RUNNING> mtu 1500 ether be:ec:9e:2b:6f:1f txqueuelen 0 (Ethernet) RX packets 33 bytes 2715 (2.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 232 bytes 29070 (28.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethd1667ac: flags=67<UP,BROADCAST,RUNNING> mtu 1500 ether 66:87:fc:c8:62:e5 txqueuelen 0 (Ethernet) RX packets 125516 bytes 459144369 (437.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 199405 bytes 18094943 (17.2 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:d8:d3:7f txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I now only have the VM on a physical NIC, watched entire 1 hour program (could never do that before), and it worked very well! What else can I provide?... Syslog/diagnostics attached. server-diagnostics-20150611-2240.zip

I take most of that back.... Usage in this way still causes br0 to lockup, and no longer be active. Technically speaking my server is still doing it's thing, however there is no network to reach it (putty, etc... all broken). Hoping to investigate this, I went to the terminal and typed in ifconfig, all looked fine, br0 still shows an IP. I attempt to run "ifconfig renew br0" (is this correct for linux?..IDK, that's basically how you do it in Windows) it fails, states "br0: host name lookup failure". If I just unplug/re-plug the network cable, everything starts to work again!. So for now I removed the virtio bridge br0 section from my VM, will see how it goes with just the physical pass thru NIC for connecting.

I think my CouchPotato is having this issue.. I had no idea, it just wouldn't work for a while. A quick bridge/host fixed it, now I think it's broke again. Results cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 192.168.1.1 # /etc/resolv.conf.tail can replace this line cat /etc/hosts # Generated 127.0.0.1 Server localhost docker exec CouchPotato cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 192.168.1.1 docker exec CouchPotato cat /etc/hosts 172.17.0.9 f7a6e8729f82 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters docker exec CouchPotato cat /etc/hostname f7a6e8729f82 I am attempting to refresh the charts, it fails, will not grab info... I could just be being impatient, however I had no idea last time (wasn't downloading anything for weeks) and I had the same symptom for the charts being empty and not refreshing. This does not look like that bug - the bug shows itself when /etc/resolve.conf on the host (unRaid) does not match /etc/resolve.conf in the container. They are supposed to, and the fact they don't is the "bug". Alright well that's good to know for that reason, and I suppose unrelated then, but I will mention it here and take it to its respective thread if completely unrelated. For this specific container (CouchPotato)the charts over time fail to load (which also means movies don't download as it can't get a connection out to check), stopping it, nor restarting the container fixes this... The charts error out on load with something snazzy like "damn, maybe you should enable some charts?" or something of that nature. You hit refresh, it seems to fail instantly. Stop it, flip host/bridge, all is fixed, working like a champ....

Picked up a $10 Intel PCie NIC (eBay), passed to the W8 VM, (maybe a bit premature, however) it does exactly what I wanted it to do, extremely well... Transfers are as fast as bare metal, etc.... One question.... Is there a simple way to tell W8 to use the Virtio KVM network by default for everything, and just use the other NIC for my media center/sharing purposes to clients? It doesn't REALLY matter, but would be nice to say, always use Ethernet 1 unless the request is specifically set to the other NIC's IP address. Maybe it does this by default? Edit: I found the answer for priority (Windows had it by default the wrong way... my luck!) http://www.eightforums.com/tutorials/20148-network-connection-priority-change-windows.html

I think my CouchPotato is having this issue.. I had no idea, it just wouldn't work for a while. A quick bridge/host fixed it, now I think it's broke again. Results cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 192.168.1.1 # /etc/resolv.conf.tail can replace this line cat /etc/hosts # Generated 127.0.0.1 Server localhost docker exec CouchPotato cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 192.168.1.1 docker exec CouchPotato cat /etc/hosts 172.17.0.9 f7a6e8729f82 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters docker exec CouchPotato cat /etc/hostname f7a6e8729f82 I am attempting to refresh the charts, it fails, will not grab info... I could just be being impatient, however I had no idea last time (wasn't downloading anything for weeks) and I had the same symptom for the charts being empty and not refreshing.

Yes

I think that it's a little bit of both.... The use case is certainly the minority for these chipsets/controllers, and I believe for that reason not much thought is put into it. I kind of expected to see information in my MB manual regarding this similar to how IRQ mapping and shared ports used to be laid out years ago (apparently they don't do that anymore, I guess I'm getting old!). The addition of the bus widths/channels should certainly help to route for proper isolation on non-consumer grade chipsets/hardware. It is also a plus that the CPU has support for isolation on downstream ports!.. Most MB's that we use are more focused for multiple GPU's that have SLI or Crossfire in use, however I am surprised that doesn't require isolation to work properly (haven't researched, making some assumptions here). I have done further testing using the downstream override option, and it hasn't lead to any issues that I've noticed yet (still a bit flakey at times with pass-thru in general, however I also just seem to be un-lucky ).

No worries, let's geek out and chat about it when you're not so pressed for time!

I guess I don't record THAT much, but have always had the ability. Moving it later to a share wouldn't help for my primary watching habits. I will attempt linking the drive as suggested, however the topic in general has been talked about plenty with WMC over time, and I'm pretty sure a local drive is unfortunately required. I didn't expect this to be as big of a pain as it is!.. If I want to stick with WMC then I think the best way to fix this is to pass the VM a physical NIC card, which should fix this issue without any trickery.

I haven't tried version 100, maybe I'll try that. Moving them to the server could work for some things, however more often than not I start watching a show in the middle of it, so at that point I need it to stream from the original location.

Windows Media Center doesn't "do" recording to mapped drives... LOL. I attempted to force it (regedit), it wasn't happy.

I am attempting to setup a Windows 8.1 VM that uses WMC to record shows and serves them to all Kodi clients using ServerWMC. This method works very well on my local HTPC, however I am trying to move this function to my server. Passing through my tuner seems to work fine, VM seems stable overall, I have recorded 4 HD shows simultaneously to an image that is the D:\ drive in Windows,and it worked flawlessly! However I need to then share that Recorded TV path in ServerWMC to share to the Kodi clients. This ends up being \\Win8VM\Recorded TV. This does not work well at all, transfers are super slow, choppy, and unreliable (I tried to just copy a show from that share to my local computer, it didn't go so well). If I am able to get LiveTv working on a client it will eventually freeze, my server is then unreachable over the LAN, no main page, no Putty connection... The console is still working like a champ however, so I run the powerdown script, and everything comes back up. I have thought of others ways to share these recordings, but nothing works very well. I need them to be accessible right away (so no copy to the server, then share) as the live tv buffer requires it. I thought maybe it was the image I pass to Windows as D:\, so I passed in a SATA card, and recorded to an actual HDD, same problem. It seems to me that Virtio doesn't like to have a virtual connection to my VM, and then have the VM share files through its own file sharing. So when I am accessing my Recorded TV I am directing this towards the VM that shares the files, however this has to go through Virtio and my bridge to share and access... IDK, that's my thoughts anyway. I tried the stable virtio, and also the newest release .105, same results (actually worse on .105). Anyone else trying to do something crazy like this? Sure would be nice if it worked!

Are you certain that the changes are not just moved up somewhere in the xml, and not where you put them? I had thought I had this issue also with a tuner card, however it worked every time (it in fact made me have the same thing twice, which produced an error).

Just wanted to report back and say that my cron errors have gone away, thanks for the update!

I'm hoping to start a discussion to better understand what boards properly support DMA mapping, isolation, and the ability to safely pass thru individual PCIe cards. I have read a decent amount of discussion by Alex Williamson on the topic discussing what is happening, and what is supposed to happen, however I also see a lot of people having issues and boards stating Vt-d support, and IOMMU groups, however the isolation that is supposed to be present is (from what I understand) non-existent. I have fairly newer consumer grade hardware (i7 4790s, & AsRock Z97 Extreme 4) that I planned to use for the "one box to rule them all" setup. I searched heavily with the MB selection and decided this board was perfect for my needs. 3 PCIe-16x slots (16x/8x/4x) 3 PCIe-1x slots. 8 SATA ports (2 on separate controller that was not the Marvell that has addressing issues when IOMMU (vt-d) is enabled). Anyhow, long story short by default all 6 PCIe slots are grouped within the same IOMMU C Group... Why?.. No idea... I have moved things around, etc.. and regardless of what I do they exist together. So the only option I have to assign one to a VM is the a PCI ACS Override setting (I just use downstream, however there are other for specific device selection). I decided to try a tuner card in a 1x slot to a Win7 VM that has been working rock solid... Nope, issues, nothing good in the syslog. VM is locked up, server is unreachable (even putty is dead), console still works great, invoke the powerdown script, start again. Anyhow, and sorry to rant... It'd be nice to know which motherboards people are using that properly assign PCIe slots to their own C groups for proper isolation. So, what hardware do you have? Does it properly assign the PCIe slots in isolated groups? ASRock Z97 Extreme 4 (from my testing, and understanding of how this all works) is NOT recommended for this use case. Any input, discussion, understanding of this BEFORE people buy hardware to do this type of setup I believe would be very beneficial. I am considering replacing my MB with one that can properly handle this use case, and isolate separate cards correctly. Discuss... ----------- Useful reads: https://lkml.org/lkml/2013/5/30/513 http://vfio.blogspot.com/2014/08/vfiovga-faq.html http://vfio.blogspot.com/2014/08/iommu-groups-inside-and-out.html

I believe it would be very beneficial to have a discussion involving this, as it is very unclear in the research I have done so far. For instance, I have no idea why by default every one of my Pcie slots are grouped to the same c group!.. This basically makes any use of vt-d useless, and without the downstream flag the inability to assign a card to a Vm. However, this seems like it is up to the motherboard manufacturer to address, and this is certainly not stated in any manual that I've found with a motherboard. I'd really look forward to this discussion as I have seen plenty of instabilities because of this (or so I think) enough to where I'd just prefer to buy a new motherboard that properly supports having Pcie slots in separate groups by default. ----- Edit: I started a thread to discuss, sorry for the derailment http://lime-technology.com/forum/index.php?topic=40409.msg380239#new