‹ BackHN Continuity

Thread

Virtio-nvgpu: Near-native Nvidia GPU access inside a KVM guest

155 points · 65 comments · WanjohiRyan

  1. markasoftware · · focus · HN ↗
    How is this different than gVisor&#x27;s nvproxy? <a href="https:&#x2F;&#x2F;gvisor.dev&#x2F;docs&#x2F;user_guide&#x2F;gpu&#x2F;#compatibility" rel="nofollow">https:&#x2F;&#x2F;gvisor.dev&#x2F;docs&#x2F;user_guide&#x2F;gpu&#x2F;#compatibility

    Edit: nvproxy is mentioned as the &quot;direct inspiration&quot; in the readme without mention of how this is different or why it doesn&#x27;t use nvproxy as a backend.

    1. WanjohiRyan · · focus · HN ↗
      We borrowed a lot of the architectural design from nvproxy, then built it to support graphical workloads. Plus it is reusable in such a way you can hot plug it into any microVM, cloud-hypervisor, maybe even Firecracker
      1. [deleted] · · focus · HN ↗

        [deleted]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.