December 22, 201510 yr Hi all, I've searched around the forum, tried a few things (got it working eventually) but I'm not comfortable with the fix and wanted to run it by some knowledgeable people to see if there's an alternative (or an official fix in the pipeline). Basically, I'm trying to pass my GTX960 through. Without changing anything, the VM errors out with: Execution error internal error: early end of file from monitor: possible problem: 2015-12-22T06:41:59.445375Z qemu-system-x86_64: -device vfio-pci,host=84:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2015-12-22T06:41:59.445410Z qemu-system-x86_64: -device vfio-pci,host=84:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 25 2015-12-22T06:41:59.445420Z qemu-system-x86_64: -device vfio-pci,host=84:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 25 2015-12-22T06:41:59.445433Z qemu-system-x86_64: -device vfio-pci,host=84:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2015-12-22T06:41:59.445446Z qemu-system-x86_64: -device vfio-pci,host=84:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized Group 25 of course being my GPU. PCI devices are as such: 00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) 00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 (rev 22) 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) 00:09.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22) 00:13.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 22) 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 22) 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) 00:14.3 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers (rev 22) 00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 06:04.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) 80:00.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 22) 80:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) 80:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) 80:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 (rev 22) 80:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) 80:09.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22) 80:13.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 22) 80:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 22) 80:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) 80:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) 80:14.3 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers (rev 22) 80:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 80:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 83:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 84:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) 84:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) ff:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) ff:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) ff:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) ff:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) ff:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) ff:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) ff:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) ff:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) ff:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) ff:03.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder (rev 02) ff:03.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers (rev 02) ff:03.4 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers (rev 02) ff:04.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control (rev 02) ff:04.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address (rev 02) ff:04.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank (rev 02) ff:04.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control (rev 02) ff:05.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control (rev 02) ff:05.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address (rev 02) ff:05.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank (rev 02) ff:05.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control (rev 02) ff:06.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control (rev 02) ff:06.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address (rev 02) ff:06.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank (rev 02) ff:06.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control (rev 02) IOMMU groups are as such: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:03.0 /sys/kernel/iommu_groups/3/devices/0000:00:05.0 /sys/kernel/iommu_groups/4/devices/0000:00:07.0 /sys/kernel/iommu_groups/5/devices/0000:00:09.0 /sys/kernel/iommu_groups/6/devices/0000:00:13.0 /sys/kernel/iommu_groups/7/devices/0000:00:14.0 /sys/kernel/iommu_groups/7/devices/0000:00:14.1 /sys/kernel/iommu_groups/7/devices/0000:00:14.2 /sys/kernel/iommu_groups/7/devices/0000:00:14.3 /sys/kernel/iommu_groups/8/devices/0000:00:16.0 /sys/kernel/iommu_groups/8/devices/0000:00:16.1 /sys/kernel/iommu_groups/8/devices/0000:00:16.2 /sys/kernel/iommu_groups/8/devices/0000:00:16.3 /sys/kernel/iommu_groups/8/devices/0000:00:16.4 /sys/kernel/iommu_groups/8/devices/0000:00:16.5 /sys/kernel/iommu_groups/8/devices/0000:00:16.6 /sys/kernel/iommu_groups/8/devices/0000:00:16.7 /sys/kernel/iommu_groups/9/devices/0000:00:1a.0 /sys/kernel/iommu_groups/9/devices/0000:00:1a.1 /sys/kernel/iommu_groups/9/devices/0000:00:1a.2 /sys/kernel/iommu_groups/9/devices/0000:00:1a.7 /sys/kernel/iommu_groups/10/devices/0000:00:1d.0 /sys/kernel/iommu_groups/10/devices/0000:00:1d.1 /sys/kernel/iommu_groups/10/devices/0000:00:1d.2 /sys/kernel/iommu_groups/10/devices/0000:00:1d.7 /sys/kernel/iommu_groups/11/devices/0000:00:1e.0 /sys/kernel/iommu_groups/11/devices/0000:06:04.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.2 /sys/kernel/iommu_groups/12/devices/0000:00:1f.3 /sys/kernel/iommu_groups/13/devices/0000:01:00.0 /sys/kernel/iommu_groups/14/devices/0000:01:00.1 /sys/kernel/iommu_groups/15/devices/0000:80:00.0 /sys/kernel/iommu_groups/16/devices/0000:80:01.0 /sys/kernel/iommu_groups/17/devices/0000:80:03.0 /sys/kernel/iommu_groups/18/devices/0000:80:05.0 /sys/kernel/iommu_groups/19/devices/0000:80:07.0 /sys/kernel/iommu_groups/20/devices/0000:80:09.0 /sys/kernel/iommu_groups/21/devices/0000:80:13.0 /sys/kernel/iommu_groups/22/devices/0000:80:14.0 /sys/kernel/iommu_groups/22/devices/0000:80:14.1 /sys/kernel/iommu_groups/22/devices/0000:80:14.2 /sys/kernel/iommu_groups/22/devices/0000:80:14.3 /sys/kernel/iommu_groups/23/devices/0000:80:16.0 /sys/kernel/iommu_groups/23/devices/0000:80:16.1 /sys/kernel/iommu_groups/23/devices/0000:80:16.2 /sys/kernel/iommu_groups/23/devices/0000:80:16.3 /sys/kernel/iommu_groups/23/devices/0000:80:16.4 /sys/kernel/iommu_groups/23/devices/0000:80:16.5 /sys/kernel/iommu_groups/23/devices/0000:80:16.6 /sys/kernel/iommu_groups/23/devices/0000:80:16.7 /sys/kernel/iommu_groups/24/devices/0000:83:00.0 /sys/kernel/iommu_groups/25/devices/0000:84:00.0 /sys/kernel/iommu_groups/25/devices/0000:84:00.1 /sys/kernel/iommu_groups/26/devices/0000:ff:00.0 /sys/kernel/iommu_groups/26/devices/0000:ff:00.1 /sys/kernel/iommu_groups/27/devices/0000:ff:02.0 /sys/kernel/iommu_groups/27/devices/0000:ff:02.1 /sys/kernel/iommu_groups/27/devices/0000:ff:02.2 /sys/kernel/iommu_groups/27/devices/0000:ff:02.3 /sys/kernel/iommu_groups/27/devices/0000:ff:02.4 /sys/kernel/iommu_groups/27/devices/0000:ff:02.5 /sys/kernel/iommu_groups/28/devices/0000:ff:03.0 /sys/kernel/iommu_groups/28/devices/0000:ff:03.1 /sys/kernel/iommu_groups/28/devices/0000:ff:03.2 /sys/kernel/iommu_groups/28/devices/0000:ff:03.4 /sys/kernel/iommu_groups/29/devices/0000:ff:04.0 /sys/kernel/iommu_groups/29/devices/0000:ff:04.1 /sys/kernel/iommu_groups/29/devices/0000:ff:04.2 /sys/kernel/iommu_groups/29/devices/0000:ff:04.3 /sys/kernel/iommu_groups/30/devices/0000:ff:05.0 /sys/kernel/iommu_groups/30/devices/0000:ff:05.1 /sys/kernel/iommu_groups/30/devices/0000:ff:05.2 /sys/kernel/iommu_groups/30/devices/0000:ff:05.3 /sys/kernel/iommu_groups/31/devices/0000:ff:06.0 /sys/kernel/iommu_groups/31/devices/0000:ff:06.1 /sys/kernel/iommu_groups/31/devices/0000:ff:06.2 /sys/kernel/iommu_groups/31/devices/0000:ff:06.3 As far as I can see, my GPU is not sharing any groups, so it shouldn't be a problem? I've enabled PCIe ACS Override, which didn't work. I've edited my syslinux.cfg file to include append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot, which stopped the error, but nothing was coming up on screen. I recreated the VM using OVMF instead of SeaBIOS, and now I'm up and running. I don't know what performance is like yet, still installing. So I've had to jump through a few hoops to get it to work, but I'm not sure this is the optimal solution? The one thing I haven't tried yet is another PCIe slot, but I'd like to get this one to work since I'll be adding a second GPU afterwards, so I'll need this one working anyway. Running the current version of unRAID - 6.1.6 And the XML incase it's needed: <domain type='kvm' id='4'> <name>Legion_Scrapz</name> <uuid>172e9a88-598b-fec9-4ee3-bcab09bd8540</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> <loader type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vdisks/Legion_Scrapz/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/ArrayVdisks/Legion_Scrapz/vdisk2.img'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/Windows 10 Pro 64bit.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.112.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:08:12:6b'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Legion_Scrapz.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x84' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x84' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc24d'/> <address bus='1' device='3'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc537'/> <address bus='1' device='2'/> </source> <alias name='hostdev3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> Any ideas? Thanks!
December 22, 201510 yr If you dont have integrated graphics an nvidea card has problems if it is the primary gpu http://lime-technology.com/forum/index.php?topic=44258.msg422520#msg422520
December 22, 201510 yr He does have a matrox card that is that main graphics it looks like. If you have it working with ovmf I wouldn't worry
December 22, 201510 yr Author Yeah, onboard graphics as main. I'm not too concerned about using OVMF, my main concern is jumping through ACS hoops for an issue I don't appear to have. But right now, I've got bigger problems. The whole tower locked up this morning, forcing me to hard reboot (another parity check... yay), and all my vdisks got dropped from the config. Trying to reattach them and it looks like they're not getting recognised, so I just keep getting a UEFI shell on boot. I'll look into this separately. When was 6.2 coming out?
December 23, 201510 yr If your vdisk got lost it might be that you didn't set the vdisk share to cache only?
December 23, 201510 yr Author vdisks are set to cache only, and there's plenty of space. The vdisk img files are there, they just don't get recognised when the VM boots. There's also still the issue of the whole system being unresponsive (couldn't even ping the server). After spending most of the day reading around, I might just have to wait until 6.2
December 23, 201510 yr Try to edit the VM and remove the install iso and then start the VM. If that doesnt work you can type exit when you get to the command prompt and you get to the bios and can go to the boot manager (or something like that. 3rd option I think) and choose efi misc device from the list.
December 23, 201510 yr Author Tried that, and that. I've turfed the VM, updated the BIOS on my GPU, and I've recreated the VM using SeaBIOS (as it's letting me now) which from what I've read - if I've read correctly - is currently more stable. I guess we'll see how this goes.
December 24, 201510 yr Author Just to keep those in the loop... I had another lock-up overnight (yet another parity check), so I started over with an updated build of a Windows 10 ISO (SW_DVD5_Win_Pro_10_1511_64BIT_English_MLF_X20-82416.ISO), after seeing elsewhere in the forum that someone else was having similar issues after installing Windows 10 using an earlier ISO and then updating the build via Updates. So the steps I took are: Updated GPU BIOS - https://www.techpowerup.com/vgabios/ Edited syslinux.cfg to include the unsafe interrupts line Created a VM with SeaBIOS, and HyperV options off Used an updated build of Windows 10 for the initial installation Time will tell, but I've been able to transfer over 250GB of data to the new VM without a crash, which is something I've been unable to do previously. Still doesn't explain my first issue, since according to the System Information, my GPU was not sharing any resource groups (I tried a different PCIe slot for the hell of it), so I shouldn't have had an issue in the first place. But if this works I'll take it. Edit: Spoke too soon.
December 26, 201510 yr Author Ok, so. I tried a Windows 7 VM, and it locked up as well. I'm now running both a Win10 and a Win7 VM with no GPU passthrough (using VNC) and things have run stable overnight. I can only assume that the passing through of my GTX960 is causing the lockups (so my first issue and second issue are actually the same thing). I am really quite out of ideas. Anyone care to shed some light on this?
December 30, 201510 yr Since you're having passthrough issues with SeaBIOS, try OVMF And see Jonp's post: Ok, the VM not booting is actually a known issue with OVMF. If you type the following commands at the UEFI shell, you can force it to boot: fs0: cd efi cd boot bootx64.efi After powering off or rebooting the server, my VM lands at the efi shell instead of booting Windows 10. The steps to launch bootx64.efi jonp shared are the only way I can boot Windows 10. I think in another thread it was pointed out that Windows 7 doesn't support UEFI, hence won't work in OVMF. Last tip that has come up in 2 recent threads - be sure to pass through BOTH the HDMI Audio and Video portions of the 960. Others confirmed it does not work passing through only the video portion of the card.
December 30, 201510 yr Author Already tried that, as mentioned in reply #3. I've since tried all manner of combinations with SeaBIOS/OVMF/i440fx/Q35. Best I got was OVMF+Q35 that gave me a "code 10" in Windows for the GPU. I only ever passed through both sound and video if passing through anything at all. I've also spent some time reading around on QEMU/KVM forums, trying little tricks and editing the XML. I have experienced issues similar to the i915 VGA arbiter issue, but apparently that doesn't apply to unraid, so... I've actually given up and switched everything off. I'm just going to wait until 6.2 to see what happens.
Archived
This topic is now archived and is closed to further replies.