GPU-PV on plain KVM, a PXE boot bug under everything, and a lawyer’s V100 monster

Homelab Highlights for 2026-11-06: self-hosting and homelab notes worth knowing.

[Audio embed placeholder]

The Lead: Hyper-V GPU-PV running on plain KVM, no passthrough

A ~600-line QEMU patch plus a Python daemon that pretends to be a Hyper-V host lets Windows VMs use the host’s GPU directly via the normal NVIDIA Windows driver. No VFIO, no vGPU, no SR-IOV. On a 9950X3D with an RTX 5090, compute hits 115-119 TFLOPS, VRAM copies at ~1,070 GB/s, and Vulkan/OpenGL pixel tests match the host exactly. The code is going public in a repo called guesthouse.

Why it matters: This is the first practical approach to shared GPU acceleration on KVM that keeps the host’s desktop working. For homelab users running Windows VMs alongside Linux, it could replace the trade-offs of full passthrough.

Source: r/Proxmox

News Roundup

UEFI Firmware RCE: How to Harden Your Self-Hosted Servers Right Now

CVE-2026-97631 is a critical 9.5-rated out-of-bounds write in the PXE network boot driver of EDK II, the open-source UEFI reference code. The vulnerable code dates to 2010 and affects firmware across a broad range of server hardware. As of late October, no fixed stable EDK II release exists, so the practical mitigation is to disable PXE boot on every server that doesn’t need it.

Why it matters: This vulnerability sits below the OS, meaning a successful exploit can survive a full reinstall. For homelab users running Proxmox, NAS, or bare-metal Docker hosts, disabling PXE is the only effective mitigation until vendors ship firmware updates.

Source: dev.to

Early release: a plugin that limits what each Jellyfin API key can access

Every Jellyfin API key is a full admin key. This new plugin, API Key Middleware, scopes each key to an allowlist of HTTP method and path. New keys start in audit mode, showing what they actually call, then you flip them to enforce. It fails open if the plugin doesn’t load after an upgrade.

Why it matters: For homelab users who hand API keys to dashboards and scripts, this plugin closes a significant security gap. It’s a practical way to limit blast radius from a leaked key without waiting for a core Jellyfin change.

Source: r/jellyfin

Turning an Old Echo Dot into a Local Voice Assistant

A 2018 Echo Dot was rooted and turned into a fully local Home Assistant voice satellite using the echo-dot-assist project. It keeps Amazon’s microphone array and wake word engine but runs Whisper and Piper locally, so voice commands never leave the house. The project now supports eight Echo models, six of which need only a micro-USB cable.

Why it matters: This is a practical way to repurpose old smart speakers into privacy-respecting voice assistants. For homelab users with a drawer full of old Echos, it’s a low-cost path to local voice control.

Source: dev.to

Tool & Software Highlight: SUB/WAVE: turn your Navidrome library into a 24/7 radio station, now one click in CA

SUB/WAVE turns a Navidrome music library into a 24/7 Icecast radio station with a DJ that picks tracks and speaks between songs. It can run fully local with Ollama and Piper, and on Unraid it’s a one-click install from Community Applications. If the LLM goes down, music keeps playing.

Why it matters: This is a polished, easy-to-setup tool that adds a fun, radio-like experience to a self-hosted music library. The local-only option and graceful failure mode make it suitable for unattended homelab use.

Source: r/unRAID

A lawyer runs DeepSeek-V4.1-Flash on eight 32GB V100s across two 4-card NVLink baseboards for private case-file work. The model is split in half across the boards (pipeline parallel 2 x tensor parallel 4), keeping heavy traffic on NVLink. It reads prompts at ~2,200 tok/s at 128K context and generates at over 200 tok/s on code. The build includes war stories about PCIe timeouts, a burnt power connector, and ECC errors fixed by dropping RAM speed.

Why it matters: This is a real-world example of running a large open model entirely in VRAM on older, cheaper datacenter hardware. The detailed build notes and troubleshooting are invaluable for anyone considering a similar high-VRAM homelab setup.

Source: r/homelab

Sources

Transcript

Host A: Welcome to Homelab Highlights, the show that surfaces practical homelab wins and useful self-hosted tools.

Host A: This one is wild. Someone on r/Proxmox got Hyper-V style GPU paravirtualization running on plain KVM. No VFIO, no vGPU, no SR-IOV. The host keeps the graphics card the entire time, and a Windows guest still gets real acceleration on it.

Host B: That is the part that sounds impossible on paper. The trick is that Windows boots under QEMU, genuinely believes it is running on Hyper-V, and just loads the normal NVIDIA Windows driver. Under the hood there is a roughly six hundred line QEMU patch for the VMBus devices, plus a Python daemon that pretends to be the Hyper-V host and talks to the NVIDIA Linux driver on the host side. Frames come out as dmabufs straight into a viewer.

Host A: The numbers are not toy numbers. On a 9950X3D with an RTX 5090 on Fedora, the poster reports compute in the 115 to 119 teraflop range, VRAM copies around a terabyte a second, and a submit round trip of about 21 microseconds. Vulkan and OpenGL pixel tests match the host exactly. D3D12, D3D11, Vulkan and OpenGL all run on the real card, and Godot’s Forward+ renderer works up to 4K.

Host B: For anyone running this at home, the shape of it matters more than the benchmark table. This is the thing full GPU passthrough never gives you: the host keeps its desktop acceleration while Windows VMs share the card. Think of a Windows-only app or a game in a VM next to your normal Linux desktop, all on one GPU. Two honest caveats from the post itself: the code is only just going public in a repo called guesthouse on GitHub, and it has only been tried on a 5090 so far. On the security side, the poster did test GPU isolation between processes, with per-process GPU page tables, and a process trying to read another’s GPU memory got nothing.

Host B: Next up, a firmware heads-up that sits underneath basically every self-hosted box. A critical vulnerability, CVE-2026-97631, was disclosed in EDK II, the open source UEFI reference code most vendor firmware is built from. It is an out-of-bounds write in the PXE network boot driver, rated 9.5, and the vulnerable code dates all the way back to 2010.

Host A: Here is the part that matters for a homelab: as of late October there is no fixed stable EDK II release yet, so most vendors have nothing to ship. The practical mitigation is configuration: disable PXE on every server that does not need it, and if a box does net boot, keep it on an isolated VLAN. The writeup also suggests the usual firmware hygiene: a strong UEFI admin password and disabling unused features.

Host B: From firmware to media servers, a new Jellyfin plugin called API Key Middleware tackles an annoying reality: every API key in Jellyfin is effectively a full admin key. The plugin scopes each key to an allowlist of HTTP method and path. New keys start in audit mode, you review what the key actually called, then flip it to enforce. One caveat the author flags plainly: it fails open, so if the plugin fails to load after an upgrade, keys get full access again.

Host A: And a quick one for the drawer archaeologists. A developer took a 2018 Echo Dot, rooted it, and turned it into a fully local voice satellite for Home Assistant using a project called echo-dot-assist. It keeps Amazon’s genuinely good microphone array and wake word engine, strips the Alexa software, and runs Whisper and Piper locally, so the command never leaves the house. The project now supports eight Echo models, and six of them need nothing more than a micro-USB cable, no soldering.

Host A: So, SUB/WAVE. The idea is simple and a little delightful: instead of hitting shuffle on a music library, the whole thing behaves like a radio station. One always-on stream, a DJ who picks the next track and says a few words between songs. It runs off a Navidrome library and streams through Icecast, so it plays anywhere a stream plays: a browser, VLC, a Sonos, even the car.

Host B: The setup story is what makes this worth the segment. On Unraid it is now a one-click install from Community Applications, and the author reports about five minutes start to finish: install, set an admin password and appdata path, then a web wizard asks for the Navidrome login, which language model to use, and a voice. Then the fun part, designing the DJ: a name, a short personality sketch, and dials for how chatty, funny, or warm they are.

Host A: What’s genuinely nice here is that it can run entirely local. Point it at Ollama for the DJ’s brain and use the built-in Piper voice; cloud models are optional, not required. And the failure mode is graceful: if the model goes down or the DJ is muted, the music keeps playing and just goes quiet between tracks. That is the right design for something meant to run unattended. One practical note from the author for Unraid users specifically: if appdata lives on a cache pool, use the cache path rather than the user share path, because the library cache is SQLite and does not get along with the FUSE layer.

Host B: For the community highlight, an update from a regular on r/homelab: the lawyer with the V100 server. The short version is that one box in the pile now runs DeepSeek-V4.1-Flash, a large open model, with a 524K token context, and it does real work every day: private first-pass reading of case files. Documents never leave the office. It pulls out facts, dates and numbers, summarizes, and takes a first swing at routine drafting, with nothing going out the door without actual review.

Host A: The hardware thesis is the fun part. SXM2 V100s on four-card NVLink baseboards are, by this person’s math, still the cheapest big pool of fast VRAM available. Eight 32-gigabyte V100s across two boards, about 2,400 dollars for 128 gigabytes of NVLinked VRAM at the prices when bought, on a Threadripper PRO host. The clever bit is the split: instead of spreading every layer across all eight cards, the model is cut in half, layers on one board and layers on the other, so the heavy traffic stays on each board’s NVLink and only one handoff per step crosses PCIe.

Host B: The results back it up. Measured this week, the 2-bit quantized model reads prompts at around 2,200 tokens per second at 128K context and generates at over 200 tokens per second on code, with every expert sitting in VRAM. The war stories are half the value, though: uncapped clocks logged cards drawing well over their power limit, followed by PCIe completion timeouts and host resets, so the cards now run capped at 150 watts. A memory channel threw uncorrected ECC errors at DDR4-3200, fixed by dropping to 2666 and confirming with long memory tests. The lesson there is not V100-specific: check connectors and error counters on any heavily loaded box.

Host A: That’s Homelab Highlights for Friday. Until next time, happy hosting!