UnRAID crashes when GPU Passthrough VM is booted

[JoHimself]

Hi all, hope you are well.

 

I recently purchased a UPS for my UnRAID server and this morning decide to plug it in. I shut down the server and unplugged it from the 8-gang extension cable it was previously plugged in to. I booted the server and everything seemed OK, so I started up the VM I use for work (it has a GTX1050ti attached).

 

The server froze completely after starting the VM and wouldn't come back up without turning off the power and booting up again. When the server came back up the "Enable VMs" setting in VMManger was set to "No". I re-enabled this and tried again. I have now tried everything I can think of.

 

The machine is plugged in to the original 8-way extension and everything is as it was, but VMs still won't boot.

 

I've removed the VM and recreated it. It boots with no devices passed through.

 

Setting the primary display to VNC but still attaching the GPU makes it crash also.

 

Does anyone have any ideas what could be the cause?

[JoHimself]

In case anyone is able to answer, I got my server logging to syslog so I could see what happens. The following is displayed when I boot the VM and they're the last logs before the machine comes back up again. 10:00.0/1 is my GPU and 30:00.0 is my USB controller

Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state
Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state
Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state
Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state
Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state
Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002)
Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002)