Virtio-nvgpu: Near-native Nvidia GPU access inside a KVM guest
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Virtio-nvgpu: Near-native Nvidia GPU access inside a KVM guest
Unofficial Hacker News client; not affiliated with Y Combinator.
mcmatterson · · focus · HN ↗
WanjohiRyan · · focus · HN ↗
mcmatterson · · focus · HN ↗
Now that I have you on the hook, is there any benefit to this over virtio for a single KVM passthrough situation? I previously ran a proxmox based gaming PC setup (docs here: <a href="https://github.com/mtrudel/rabble/tree/4d9329f3dd0fb09123a8f40b7bff3329a8273b11" rel="nofollow">https://github.com/mtrudel/rabble/tree/4d9329f3dd0fb09123a8f...), and was lucky enough that the GPU passthrough part of that build 'just worked'. I'd started down a path of trying to share the GPU between VMs based on a naive 'one VM owns it at a time' setup, but never really got it off the ground.
WanjohiRyan · · focus · HN ↗
You should check out Nestri [1], another project we are working on, that helps you do exactly that. It helps run multiple gaming sessions for you and your friends on the same GPU, without anyone meddling in the other person's session. Everyone gets to stream their game to whatever desktop or device they want. It is still a work-in-progress though.
[1] <a href="https://github.com/nestrilabs/nestri" rel="nofollow">https://github.com/nestrilabs/nestri
jchw · · focus · HN ↗
junon · · focus · HN ↗
lisp2240 · · focus · HN ↗
Sorry. Qwerty isn't my native keyboard.
Fucukdyshd iohhfghfhgh ggbvfg gdh ghcfjh hdhvbbghb hjjgigggfv.q gfghbdbdbd cjcjcjcnn. Dr rhrjfnnf cjcucjcjjcnr rbjjdisnxbbfb hehrbrbrb. Xjcjcjcjbd rhrjrnrbrb xhfjcjcjbde hdhdbcncbfn dhdjjfjchcnbdbdbffnndnd