view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I've also wanted to do this for a while, but there were always a few too many barriers to actually spin up the project. Here's just a brain dump of things I've seen recently.
vGPUs continue to be behind a license. But there is now vgpu_unlock.
L1T just showed off PCIe "fabric" from Liqid that can switch physical devices between machines.
Turning VMs on and off isn't as slick as either of the above, but that is doable today. You'll just have to build all the switching automation yourself. That could just be a shell script running QEMU/libvirt commands, at a minimum.
Here is an alternative Piped link(s):
L1T just showed off PCIe "fabric" from Liqid that can switch physical devices between machines.
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Why are vGPUs behind a license? They work fine on Linux as they are part of KVM and Virtio.
Why? Product segmentation I suppose. Last I looked, the Virtio project's efforts were still work-in-progress. The Arch wiki article corroborates that today. Inconsistent behavior across brands and product lines.
What are you talking about? I though we were talking about Proxmox
The OP didn't mention Proxmox in their post. I've been speaking generally, not about any specific OS. For example, Nvidia's enterprise offerings include a license to use their "GRID" vGPU tech (and the enabled feature flag in the driver).
Thank you