Re: [qubes-users] "kfd kfd: error getting iommu info. is the iommu enabled?"
Claudia: > January 4, 2020 9:35 AM, "awokd' via qubes-users" > wrote: >> The Xen logs look similar to mine. I don't have kfd on my system. > > From what I saw, I think kfd is an AMD thing. Do you have AMD? Yes. Pre-Ryzen, but the AMD IOMMU init in Xen logs looks the same. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1fe5a095-12f9-b394-263c-540432eba4d4%40danwin1210.me.
Re: [qubes-users] "kfd kfd: error getting iommu info. is the iommu enabled?"
January 4, 2020 9:35 AM, "awokd' via qubes-users" wrote: > Claudia: > >> I'm getting this message in my logs, about an IOMMU error, on both 4.0.2 and >> the F31-based 4.1 >> build. I'm as certain as I can be that the IOMMU is enabled in BIOS. I'm >> having issues with >> passthru and I'm wondering if this might be the cause. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1404139 >> This thread says it's not a bug, it's just because the system doesn't >> support IOMMUv2 and amdkfd >> (whatever that is) requires IOMMUv2 (whatever that is) for HSA (whatever >> that is). I don't really >> know what any of that means. >> >> Or does it just mean that my GPU is not protected by the IOMMU (same as >> iommu=no-igfx on Intel) and >> I don't have to worry about it? > > I saw in a different thread you made progress, so this is probably > outdated. However, I think your conclusions are correct. If your IOMMU > was not working correctly, you would have problems starting HVMs period. > I made progress on a couple of things, but not USB Qube. I was just wondering if might have something to do with USB controller passthru. However it may be that USB Qube is simply not supported on this system due to IOMMU grouping. Other passthru HVMs such as sys-net work fine, though, so I guess that means the IOMMU is working despite the error. > The Xen logs look similar to mine. I don't have kfd on my system. >From what I saw, I think kfd is an AMD thing. Do you have AMD? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2d227faa21653704c60f57d5032e684a%40disroot.org.
Re: [qubes-users] "kfd kfd: error getting iommu info. is the iommu enabled?"
Claudia: > I'm getting this message in my logs, about an IOMMU error, on both 4.0.2 and > the F31-based 4.1 build. I'm as certain as I can be that the IOMMU is enabled > in BIOS. I'm having issues with passthru and I'm wondering if this might be > the cause. > https://bugzilla.redhat.com/show_bug.cgi?id=1404139 > This thread says it's not a bug, it's just because the system doesn't support > IOMMUv2 and amdkfd (whatever that is) requires IOMMUv2 (whatever that is) for > HSA (whatever that is). I don't really know what any of that means. > Or does it just mean that my GPU is not protected by the IOMMU (same as > iommu=no-igfx on Intel) and I don't have to worry about it? I saw in a different thread you made progress, so this is probably outdated. However, I think your conclusions are correct. If your IOMMU was not working correctly, you would have problems starting HVMs period. The Xen logs look similar to mine. I don't have kfd on my system. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ebc3a9f9-c7c8-477d-6d85-e2a76b9ea33f%40danwin1210.me.
[qubes-users] "kfd kfd: error getting iommu info. is the iommu enabled?"
I'm getting this message in my logs, about an IOMMU error, on both 4.0.2 and the F31-based 4.1 build. I'm as certain as I can be that the IOMMU is enabled in BIOS. I'm having issues with passthru and I'm wondering if this might be the cause. In dom0 kernel logs: AMD IOMMUv2 driver by Joerg Roedel https://community.amd.com/thread/170292 This thread recommends creating /etc/udev/rules.d/kfd.rules with MODE="0666". Qubes 4.1 has file /usr/lib/udev/rules.d/50-udev-default.rules which contains: SUBSYSTEM=="kfd", GROUP="render", MODE="0666" although 4.0.2 appears to have no such file. However I get the same error even on 4.1 so I don't think that's the fix. https://unix.stackexchange.com/questions/263901/kfd-error-getting-iommu-info This thread says add kernel parameter "iommu=pt" but I don't know if that's effective or safe in Qubes, because Xen handles the IOMMU instead of the kernel I think. I'm not really sure what that parameter does. https://bugzilla.redhat.com/show_bug.cgi?id=1404139 This thread says it's not a bug, it's just because the system doesn't support IOMMUv2 and amdkfd (whatever that is) requires IOMMUv2 (whatever that is) for HSA (whatever that is). I don't really know what any of that means. Is it an error? Should I be worried? Could it be causing my passthru problems? Or does it just mean that my GPU is not protected by the IOMMU (same as iommu=no-igfx on Intel) and I don't have to worry about it? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/22518f58b4489a980ec75ccce0e7d71b%40disroot.org.
