XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Nvidia MiG Support

    Scheduled Pinned Locked Moved Compute
    gpugpu passthrough
    23 Posts 5 Posters 7.5k Views 7 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      Dani @olivierlambert
      last edited by

      @olivierlambert OMG! It's true.
      It would be a funny situation if you pay Citrix premium license to virtualize the A100 and it's not compatible 😵
      Next time i'll check HCL first 😬

      Thanks Olivier

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        I'm sure they are working on something, since it's a BIG market for them 🙂 Let's stay tuned!

        1 Reply Last reply Reply Quote 0
        • andSmvA Offline
          andSmv Vates 🪐 XCP-ng Team Xen Guru
          last edited by andSmv

          Hello, I'm honestly don't know how Citrix vGPU stuff works, but couple of thoughts on this topic:

          If I understand correctly, you say Nvidia use VFIO Linux framework to enable mediated devices which can be exported to guest. The VFIO framework isn't supported by XEN, as VFIO need the presense of IOMMU device managed by IOMMU Linux kernel driver. And XEN doesn't proide/virtualize IOMMU access to dom0 (XEN manages IOMMU by itself, but doesn't offer such access to guests)

          Bascally to export SR-IOV virtual function to guest with XEN you don't have to use VFIO, you can just assign the virtual function PCI "bdf" id to guest and normally the guest should see this device.

          From what I understand Nvidia user-mode toolstack (scripts & binaries) doesn't JUST create SR-IOV virtual functions, but want to access VFIO/MDEV framework, so all this thing fails.

          So may be, you can check if you there's some options with Nvidia tools to just create SR-IOV functions, OR try to run VFIO in "no-iommu" mode (no IOMMU presence in Linux kernel required)

          BTW, we working on some project where we are intending to use VFIO with dom0, and so we're implementing the IOMMU driver in dom0 kernel, so it would be interesting to know in the future, if this can help with your case.

          Hope this help

          1 Reply Last reply Reply Quote 0
          • Z zxcp referenced this topic on
          • First post
            Last post