billyth01 Posted August 24, 2018 Posted August 24, 2018 I'm trying to start the windows 10 machine but it won't work. I think it's a error to do with groups. qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio error: 0000:03:00.0: failed to setup container for group 16: failed to set iommu for container: Operation not permitted
Squid Posted August 24, 2018 Posted August 24, 2018 Post your diagnostics so that the persons most able to help will be able to
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 7 minutes ago, Squid said: Post your diagnostics so that the persons most able to help will be able to Like what kind of diagnostics? Im sorry I'm new to unraid ?
itimpi Posted August 24, 2018 Posted August 24, 2018 2 minutes ago, billyth01 said: Like what kind of diagnostics? Im sorry I'm new to unraid ? Go to Tools->Diagnostics and it will create a zip file containing lots of useful information for diagnosing the cause of problems. Upload the current zip here to get feedback.
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 Just now, itimpi said: Go to Tools->Diagnostics and it will create a zip file containing lots of useful information for diagnosing the cause of problems. Upload the current zip here to get feedback. tower-diagnostics-20180824-1506.zip
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 37 minutes ago, Squid said: Post your diagnostics so that the persons most able to help will be able to tower-diagnostics-20180824-1506.zip
1812 Posted August 24, 2018 Posted August 24, 2018 you need to also passthrough the audio portion of the gpu you're trying to use.
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 1 minute ago, 1812 said: you need to also passthrough the audio portion of the gpu you're trying to use. It gave me the same error
1812 Posted August 24, 2018 Posted August 24, 2018 7 minutes ago, billyth01 said: It gave me the same error then you need to post new diagnostics after it fails again. see next post.
1812 Posted August 24, 2018 Posted August 24, 2018 wait, I see it now: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform you can find the solution to enable unsafe interrupts in the link in my sig for proliant information (same procedure.) after making the modification to your syslinux.cfg, reboot and retry again.
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 8 minutes ago, 1812 said: wait, I see it now: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform you can find the solution to enable unsafe interrupts in the link in my sig for proliant information (same procedure.) after making the modification to your syslinux.cfg, reboot and retry again. I'm rebooting now
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 18 minutes ago, 1812 said: wait, I see it now: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform you can find the solution to enable unsafe interrupts in the link in my sig for proliant information (same procedure.) after making the modification to your syslinux.cfg, reboot and retry again. Oops didn't do the whole thing ill try again
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 28 minutes ago, 1812 said: wait, I see it now: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform you can find the solution to enable unsafe interrupts in the link in my sig for proliant information (same procedure.) after making the modification to your syslinux.cfg, reboot and retry again. Ok now it says the same thing for group 14
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 Do I have to do it for gui mode instead? I did it for unsaid os and that's it
1812 Posted August 24, 2018 Posted August 24, 2018 10 minutes ago, billyth01 said: Do I have to do it for gui mode instead? I did it for unsaid os and that's it do it for whatever mode you are booting into. since you've made a change to the syslinux.cfg, after getting the error, now post fresh diags
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 Now it says it started and it won't show anything on the screen
billyth01 Posted August 24, 2018 Author Posted August 24, 2018 This is the new one tower-diagnostics-20180824-1637.zip
1812 Posted August 24, 2018 Posted August 24, 2018 13 minutes ago, billyth01 said: Now it says it started and it won't show anything on the screen could be a number of things, like needing the gpu rom file passed to the gpu to any of this: https://www.google.com/search?q=unraid+gpu+black+screen
Recommended Posts
Archived
This topic is now archived and is closed to further replies.