SU11YBEAR Posted June 4, 2016 Share Posted June 4, 2016 Been trying to setup unRAID for about a day now and seem to be moving backwards Initial setup was an AsRock 990Fx Fatality with 1100T, 7950 and 6770, could create Win10 VM but when trying to install AMD Drivers would bluescreen and go into continual reboot. After struggling with this changed the Motherboard to an Asus Sabertooth 990FX with 8350, just trying the 6770 at the moment, can create VM's using VNC but when trying to use GPU get the following (on new creation but same error occurs when changing created VM from VNC to GPU) internal error: early end of file from monitor: possible problem: 2016-06-04T15:43:52.542821Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2016-06-04T15:43:52.542844Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 18 2016-06-04T15:43:52.542853Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 18 2016-06-04T15:43:52.542863Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-06-04T15:43:52.542873Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized Log shows no errors when I do this, think the first line might be related to the issue Jun 4 11:43:52 Tower kernel: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform Jun 4 11:43:52 Tower kernel: br0: port 2(vnet0) entered disabled state Jun 4 11:43:52 Tower avahi-daemon[1689]: Withdrawing workstation service for vnet0. Jun 4 11:43:52 Tower kernel: device vnet0 left promiscuous mode Jun 4 11:43:52 Tower kernel: br0: port 2(vnet0) entered disabled state PCI devices 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port E) 00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A) 00:0b.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (NB-SB link) 00:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port B) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) 00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) 00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) 00:15.3 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3) 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] 02:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) 0b:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 0c:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller Any help is greatly appreciated Thanks Su11ybear Quote Link to comment
Squid Posted June 4, 2016 Share Posted June 4, 2016 You also have to passthrough the audio on the video card Quote Link to comment
SU11YBEAR Posted June 4, 2016 Author Share Posted June 4, 2016 Just tried again with sound card set to the AMD device, looks to be the same error internal error: early end of file from monitor: possible problem: 2016-06-04T16:03:35.670588Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2016-06-04T16:03:35.670621Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 18 2016-06-04T16:03:35.670630Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 18 2016-06-04T16:03:35.670644Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-06-04T16:03:35.670654Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized Quote Link to comment
saarg Posted June 4, 2016 Share Posted June 4, 2016 Just tried again with sound card set to the AMD device, looks to be the same error internal error: early end of file from monitor: possible problem: 2016-06-04T16:03:35.670588Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2016-06-04T16:03:35.670621Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 18 2016-06-04T16:03:35.670630Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 18 2016-06-04T16:03:35.670644Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-06-04T16:03:35.670654Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized Did you follow the advice given in the log to enable allow_unsafe_interrupts? Add this after append in your syslinux.cfg vfio_iommu_type1.allow_unsafe_interrupts=1 Quote Link to comment
SU11YBEAR Posted June 4, 2016 Author Share Posted June 4, 2016 I had not, added the line and rebooted still having the issue sysconfig copy below default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot vfio_iommu_type1.allow_unsafe_interrupts=1 label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest log from my last try Jun 4 12:45:20 Tower kernel: device vnet0 entered promiscuous mode Jun 4 12:45:20 Tower kernel: br0: port 2(vnet0) entered listening state Jun 4 12:45:20 Tower kernel: br0: port 2(vnet0) entered listening state Jun 4 12:45:21 Tower kernel: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform Jun 4 12:45:21 Tower kernel: br0: port 2(vnet0) entered disabled state Jun 4 12:45:21 Tower avahi-daemon[1964]: Withdrawing workstation service for vnet0. Jun 4 12:45:21 Tower kernel: device vnet0 left promiscuous mode Jun 4 12:45:21 Tower kernel: br0: port 2(vnet0) entered disabled state Quote Link to comment
saarg Posted June 4, 2016 Share Posted June 4, 2016 I had not, added the line and rebooted still having the issue sysconfig copy below default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot vfio_iommu_type1.allow_unsafe_interrupts=1 label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest log from my last try Jun 4 12:45:20 Tower kernel: device vnet0 entered promiscuous mode Jun 4 12:45:20 Tower kernel: br0: port 2(vnet0) entered listening state Jun 4 12:45:20 Tower kernel: br0: port 2(vnet0) entered listening state Jun 4 12:45:21 Tower kernel: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform Jun 4 12:45:21 Tower kernel: br0: port 2(vnet0) entered disabled state Jun 4 12:45:21 Tower avahi-daemon[1964]: Withdrawing workstation service for vnet0. Jun 4 12:45:21 Tower kernel: device vnet0 left promiscuous mode Jun 4 12:45:21 Tower kernel: br0: port 2(vnet0) entered disabled state You added it in the wrong place. It should be right after appen like below. default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest Quote Link to comment
SU11YBEAR Posted June 4, 2016 Author Share Posted June 4, 2016 Thank you! It is now up and running, did switch over to another mobo (intel) i had laying around but still using AMD GPU's, its working so will keep it running with this and when i switch back will confirm the AMD mobo (might be a bit) Thanks again Saarg Quote Link to comment
itsknob Posted March 7, 2021 Share Posted March 7, 2021 On 6/4/2016 at 2:38 PM, saarg said: You added it in the wrong place. It should be right after appen like below. default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest This solved it for me! Can't thank you enough. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.