[Bug 288848] bhyve GPU passthru for NVIDIA not working
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 288848] bhyve GPU passthru for NVIDIA not working"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 13 Aug 2025 22:39:35 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
Tomoaki AOKI <junchoon@dec.sakura.ne.jp> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |junchoon@dec.sakura.ne.jp
--- Comment #1 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> ---
It would be nice if the changes can be obtained as a patch to original src
tree.
Without it, no discussion is possible, as it's almost impossible to know what's
changed throughout the whole bunch of src tree for this.
I'm on discussion you pointed and once tried to let github to generate diffs
between the branch you mentioned and seemingly corresponding branch, but it
didn't finish (no results are shown) within several hours. (As I myself don't
use GPU passthrough, I don't want to clone the repo just to obtain / generate
diffs locally. So I gave up.
(Not sure the original author did pull request or not.)
And even with the repo, fatal problems are seen in the thread.
At least different guest requires different fingerprint of the host VM (here,
bhyve), some require "KVMKVMKVM" and some others require something other,
forcing the user reporting it to rebuild FreeBSD modifying the patch to switch.
At least, the fingerprint SHALL be configurable per-instance (conf files,
sysctl,...).
Not shure how trivial the fix would be.
In my humble opinion, passing through any hardware is quite fragile and not a
recommended way. I believe making UEFI firmware (or its successor) the VM host
and forcing hardware accesses to be runtime services is the way to go, like
mainframes are doing for CPUs, memories and so on (PPAR - Physical
PARtitioning, LPAR - Logical PARtitioning, and any kind of virtualizations). As
the idea of virtual machines itself came from mainframes.
--
You are receiving this mail because:
You are the assignee for the bug.