
I've experienced others in the past, and it's very frustrating and time consuming. Which means: either one terminates the X session each time before starting/after stopping the VM (so X will handle the power management), or they leave the card owned by the vfio driver (but this makes the card run hot while sitting doing nothing, because the vfio driver doesn't handle the power management), or they swap drivers on the fly hoping that it will work fine (on nvidia, it's not a stable strategy no idea on AMD).Īnd these are just a few issues. VFIO does work, but it's hacky, so it's very inconvenient unless one has plenty of time and patience.įor example, AMD GPUs don't support rebar (took a while to figure out), and they used to have (I don't know if it's been definitely solved) a problem with reset, which caused random lockups when exiting the VM.Īdditionally, power saving/device ownership must be handled. Between my day job and a young family, don’t have as much time for personal projects as I used to, and what time I do have I’d rather expend towards other goals. My biggest concern about doing it would be the macOS kexts - will Oracle’s trademark policy allow you to redistribute their kext binaries along with a fork, or force you to rebuild them under a new ID? If the later, will Apple approve it (for any special entitlements it might use)? Not an issue for Linux and Windows builds anyway.Įven stuff like RDP, I haven’t looked at the VirtualBox code in detail, but I assume there would be some interfaces to isolate display clients from the low-level technical details of the graphics card emulation-so it might not actually require as much “low-level chops” as you might think.īut your last point about not many people want to spend their weekends on it is spot-on: I myself am not volunteering to do any of this.

You could probably even automate a lot of it, with manual intervention only required for branding-related changes (which I assume would be rare). I think a “just rebrand it and remove all mention of Oracle’s proprietary extension pack” fork wouldn’t require much “low level programming chops” at all.
