• drathvedro@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    This is, indeed, uncommon. Typically the GPU either gets detected(abeit, often with errors), or the VM doesn’t start at all. Do you use libvirt by and chance?

      • drathvedro@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        But are you launching VM via virsh/virt-manager or directly using qemu-system-x86_64? Could you provide the XML or the command line you’re using? What does lspci -k say in regards to your GPU’s?

        • BigDaddySlim@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 months ago

          Sorry for the delayed reply, don’t have much free time on work days.

          Was launching the VM via virt-manager. Do you want the overview XML or for a specific category within virt-manager?

          lspci -k shows both my GPUs are there now but trying to load the BM says iommu group is not viable

          • drathvedro@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            7 months ago

            Do you want the overview XML or for a specific category within virt-manager?

            A full XML, unless you have something private in there, which you can remove. I just remember that for nvidia’s there could be parts preventing load anywhere. In my case, for example, it was booting a BIOS VM instead of UEFI one.

            shows both my GPUs are there now

            But what’s the driver used? Should be something like this (my laptop for example, without irrelevant lines)

            01:00.0 VGA compatible controller: NVIDIA Corporation GA104 [Geforce RTX 3070 Ti Laptop GPU] (rev a1)
            	Kernel driver in use: vfio-pci
            01:00.1 Audio device: NVIDIA Corporation GA104 High Definition Audio Controller (rev a1)
            	Kernel driver in use: vfio-pci
            06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt (rev c7)
            	Kernel driver in use: amdgpu
            06:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1640
            	Kernel driver in use: snd_hda_intel
            

            the BM says iommu group is not viable

            Well that’s something. Check the script at arch wiki on VFIO, at the paragraph “2.2 Ensuring that the groups are valid”. It should print out the IOMMU groups you have in your system.

            Basically, a thing with IOMMU is that you must pass all or none of the devices down to VM within each IOMMU group, even if you don’t necessarily want them in your VM. In most cases, that means also passing the built-in sound card that feeds audio via HDMI outputs (the .1’s in the above example). In cases where there’s something else crucial in that IOMMU group, there’s ACS patch but that’s a hack and should only be used as a last resort.

            • BigDaddySlim@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              7 months ago

              Man I’ve followed like 6 different guides to a T and tried with 4 different distros and still can’t get it to work. I’m done fighting with it for a while. Maybe it’s just an issue with 7000 series AMD cards or the guides aren’t up to date with the kernals idk. I need to take a long break from it before I get upset and just return the GPU lol

              Appreciate you trying to help though, truly

              • drathvedro@lemm.ee
                link
                fedilink
                arrow-up
                2
                ·
                7 months ago

                Aight. I understand, VFIO is a kickflip of linux world and it takes a lot of pain, frustration and patience to do, so take your time.

                Also, the next time you go for it, maybe give supergfxctl a shot, if you haven’t already, if it works it should be pretty straightforward.