GPU sharing for the rest of us, a remote homelab 1,600 km away
Homelab Highlights for 2026-11-09: self-hosting and homelab notes worth knowing.
[Audio embed placeholder]
The Lead: geforce-sriov v0.2.0 beta: SR-IOV vGPU on consumer NVIDIA Ampere and Ada GPUs
A developer released version 0.2.0 beta of geforce-sriov, a toolkit that lets multiple VMs share a consumer NVIDIA GPU through SR-IOV rather than mdev. The big news is Ada support now works, tested on an RTX 4070 SUPER, with up to 4 virtual functions per card using the proprietary driver with GSP disabled. Setup is simplified to a single command, and Ampere and Ada cards can share the same host.
Why it matters: NVIDIA’s official vGPU path is for datacenter cards, not the GeForce cards most homelabs use. This project opens GPU sharing for Proxmox users who want to split one card across Jellyfin, gaming VMs, or ML workloads.
Source: r/Proxmox
News Roundup
Collimo: a read-only monitor for Proxmox, Ceph, PBS, and the rest of the rack
A Redditor built Collimo, a Docker stack that reads Proxmox VE, Ceph, and PBS through read-only audit tokens and puts them alongside NAS, UPS, PDUs, switches, BMCs, and WAN in one dashboard. Features include honest memory accounting (guest cache labeled, ZFS ARC excluded), cluster drift detection, placement advice, blast radius mapping, and backup recency checks. Closed source but free for personal use; the author seeks 20 beta testers with diverse hardware.
Why it matters: For anyone running a multi-node Proxmox cluster, this consolidates five consoles into one read-only view with smart defaults that avoid common monitoring pitfalls.
Source: r/Proxmox
Immich Mount: mounting Immich as a drive in Finder, Nautilus, or Dolphin
A developer built Immich Mount, which mounts an Immich photo library as a real drive in file managers on Linux and Mac. Browsing uses only metadata and thumbnails; full files are fetched lazily when opened. It includes an upload folder and organizes photos by year/month, albums, people, and places. Read-only except for uploads, no Windows version yet.
Why it matters: This fills the gap for households that left iCloud or Google Photos but missed having photos available as normal files for attaching to emails or inserting into documents.
Source: r/immich
ZimaBlade NAS + Router Combo: PCIe Build Guide
A guide for building a Proxmox host with OPNsense router VM and ZFS NAS on a ZimaBlade SBC. It opens with a cautionary tale of USB-enclosure backups that silently corrupted for six weeks due to a controller reset. Key warnings: the PCIe slot is physically x4 but electrically x1 on some revisions, and a PCIe SATA controller with external power is recommended for any ZFS pool.
Why it matters: The USB enclosure failure story is a stark reminder that untested backup is not a backup, and the guide provides practical architecture advice for a popular but tricky SBC.
Source: dev.to
Tool & Software Highlight: rynas: a fast, modern NAS manager for plain Debian
rynas is a web interface that turns a plain Debian 13 server into a managed NAS. It supports RAID arrays (mdadm, btrfs, ext4, LUKS2), per-bay views, SMART, spin-down, SMB/NFS shares, btrfs snapshots, Docker compose management, a curated app catalogue, and HTTPS via built-in Caddy. It’s lightweight (Rust + WebAssembly), changes are staged and roll back on network failure, and it’s AGPL-3.0. Alpha status: no ZFS yet, no apt repo.
Why it matters: For users who want a NAS UI without leaving Debian’s standard tooling, rynas offers a modern, lightweight alternative to TrueNAS or OMV that doesn’t lock you in.
Source: r/HomeServer
Community Highlight: Self-hosting a remote homelab 1,600 km away: Proxmox on a hacked Chromebox, Tailscale mesh, and bypassing CGNAT via Oracle Cloud
A developer in Mumbai runs his bare-metal homelab 1,600 km away in Kanyakumari, India. The setup: Proxmox on a hacked Chromebox, automated 3-2-1 backups, cellular failover, and a Tailscale mesh with an Oracle Cloud relay to bypass CGNAT. The post includes raw backup scripts and network configs. A comment thread highlights the need for out-of-band KVM after a grub edit locked the machine remotely.
Why it matters: This extreme remote setup illustrates the importance of out-of-band management: anything reachable only after the OS boots has a gap at exactly the wrong moment, and a JetKVM or similar device can prevent a panicked phone call home.
Source: r/selfhosted
Sources
- [Update] geforce-sriov v0.2.0 beta: SR-IOV vGPU on consumer NVIDIA Ampere and Ada GPUs - r/Proxmox
- I built a read-only monitor for Proxmox, Ceph and PBS (and the rest of the rack). Looking for 20 private beta testers - r/Proxmox
- Mounting Immich as if it was OneDrive or Google Drive - Reddit
- ZimaBlade NAS + Router Combo: PCIe Build Guide - dev.to
- rynas – a fast, modern NAS manager for plain Debian - r/HomeServer
- Self-hosting a remote homelab 1,600 km away: Proxmox on a hacked Chromebox, Tailscale mesh, and bypassing CGNAT via Oracle Cloud - r/selfhosted
Transcript
Host A: Welcome to Homelab Highlights, the show that surfaces practical homelab wins and useful self-hosted tools.
Host A: This one is for the Proxmox crowd. A developer who posted recently about getting SR-IOV vGPU working on consumer NVIDIA Ampere cards just released version 0.2.0 beta of a toolkit called geforce-sriov. Short version: multiple VMs share one consumer GeForce card through SR-IOV, instead of the mdev approach earlier vGPU unlock projects used.
Host B: And the headline in this update is Ada support. The developer borrowed a friend’s RTX 4070 SUPER and got SR-IOV vGPU working on it — extra work, because most consumer Ada cards only report one virtual function in hardware, so getting four meant patching NVIDIA’s host driver and the vGPU plugin. It supports up to four VFs per card, running the proprietary driver with GSP disabled. Ampere and Ada can even share the same host at the same time.
Host A: So why does this matter? If you run Proxmox at home and want to hand slices of one GPU to a few VMs — a Jellyfin transcode box, a Windows gaming VM, a machine learning box — NVIDIA’s official vGPU path is for datacenter cards, not the GeForce cards most homelabs use. Setup got simpler too: a single command now handles prerequisite checks, installation, driver patching, and VF activation. Run it, cold power cycle the host, run it again. Plus MSI-X support for both generations, automatic VF setup at boot, and readiness checks before VMs start.
Host B: The honest caveat: it’s beta, and only tested on dual RTX 3080s and that 4070 SUPER. Other Ampere and Ada cards should work but that’s unverified — which is why the post asks people to file compatibility reports, template linked in the repo at noon-at-cgn. Promising, genuinely new capability, but test it on hardware where a weekend of breakage doesn’t hurt.
Host B: Next up, a monitoring project that deserves a real look. A Redditor running a three-node Proxmox cluster on Ceph with a PBS box got tired of checking five consoles to answer whether everything is okay. So Collimo was born: one Docker stack that reads Proxmox VE, Ceph, and PBS through read-only audit tokens, and puts all of it next to the rest of the rack — NAS, UPS, PDUs, switches, BMCs, the WAN.
Host A: The details are what make it interesting. Memory figures are labeled honestly: a VM’s number includes guest cache, and pressure decides whether it’s actually short; a node’s used memory excludes the ZFS ARC. It flags cluster drift — nodes whose PVE build, BIOS, BMC firmware, MTU, or VLANs differ — can read BIOS on mini PCs with no BMC via Intel AMT, offers placement advice honoring HA groups and affinity rules without ever moving anything, maps blast radius per switch or UPS, matches backup recency against PBS or Veeam, and keeps reading through whichever node answers when one is down. That’s a lot of detail for a read-only dashboard. Closed source but free for personal use, everything exports, read-only throughout — the author wants about twenty beta testers, especially people with Redfish BMCs, non-UniFi switches, or Veeam and XCP-ng.
Host B: Over on r/immich: a developer who moved off iCloud built Immich Mount, which mounts a photo library as a real drive in Finder, Nautilus, or Dolphin, with years, albums, people, and places as folders. Browsing pulls only metadata and thumbnails; files fetch lazily when opened, so videos seek fine, and there’s an upload folder. Everything except that folder is read-only by design, and there’s no Windows version yet.
Host A: And a cautionary note from a ZimaBlade NAS-plus-router guide on DEV. It opens with a client whose USB-enclosure backups silently corrupted for six weeks — the controller reset under load, dropped the pool, re-imported it, and nobody noticed until a restore failed during a real incident. The guide covers Proxmox with an OPNsense VM and a ZFS NAS layer on the board, and warns the PCIe slot is physically x4 but electrically x1 on some revisions. It recommends a PCIe SATA controller like the ASM1166 or JMB585 with external power for any ZFS pool. The takeaway: test the restore path, not just the storage.
Host A: Tool spotlight this time goes to rynas from r/HomeServer — a web interface that turns a plain Debian 13 server into a managed NAS. Install Debian the usual way, add one package, manage the rest from a browser. The feature list is genuinely broad for an alpha: RAID arrays and volumes across mdadm, btrfs, ext4, and LUKS2, with a live per-bay view, SMART data, and spin-down control; SMB shares including Time Machine, NFS, quotas, a recycle bin, a web file manager; btrfs snapshots with retention, restore, and rollback; Docker compose stack management that runs alongside Portainer or Dockge; a curated catalogue of about twenty-five apps including Immich and Jellyfin; and HTTPS everywhere through a built-in Caddy with Let’s Encrypt via DNS challenge.
Host B: What stands out is the design philosophy. It’s just Debian underneath — standard tools, standard config files, standard apt updates. Uninstall rynas and the server keeps working. It’s lightweight too: a small root daemon, a Rust HTTP server, and a WebAssembly UI idling at a few megabytes. And network changes are staged and applied together, rolling back automatically if the connection drops — which stops the classic lock-yourself-out mistake. Two honest notes: no ZFS yet, though the developer says it’s coming, and it’s alpha — fine on the author’s test boxes, but the post says don’t trust it with unbacked-up data, and there’s no apt repo yet, so the .deb is built with a script. Licensing is AGPL-3.0, all features free.
Host A: There’s a fun companion project too: synodeb installs Debian 13 on Synology DS920 and DS923 hardware with everything working — fans, LEDs, buttons, every bay — and rynas on top then shows the real chassis view. Taking a Synology shell and running honest Debian on it is very appealing for anyone who liked the hardware but not DSM.
Host B: Community highlight this week is from r/selfhosted, and it takes remote homelab management to the extreme. A developer lives in an apartment in Mumbai, but the actual bare-metal homelab sits 1,600 kilometers away at the southern tip of India in Kanyakumari — Proxmox on a hacked Chromebox, running Immich, monitoring, and a Windows VM.
Host A: Because walking over to power-cycle the box isn’t an option, the whole design assumes nobody can touch it: automated 3-2-1 backups, automated cellular failover to BSNL 4G behind the primary fiber, and a Tailscale mesh with an Oracle Cloud relay to get past the ISP’s double NAT. The full write-up, including the raw backup scripts and network configs, is on the author’s blog.
Host B: The comments turned into their own lesson, though. Someone suggested a JetKVM-style device that relays HDMI and USB over the network so a machine can be reached even at the boot menu. The author’s reply sticks: a while back, while messing with Intel iGPU passthrough, an edit to the grub config hung the OS on reboot before Tailscale or SSH could come up. From Mumbai, with the photo library unreachable, the fix was calling mom, having her borrow a USB keyboard from a neighbor, and walking her through terminal commands over the phone to revert grub. Another commenter put it plainly: for a box that far away, out-of-band KVM and remotely controlled power belong in the backup plan, not the nice-to-have list — Tailscale can’t fix a bad boot config. It’s one person’s anecdote, but the shape generalizes: anything only reachable after the OS is up has a gap at exactly the wrong moment, and out-of-band access fills it.
Host A: That’s Homelab Highlights for Monday. Until next time, happy hosting!