Ah, sorry. I was answering about hyper.
The earliest reference to “meh key” I’m turning up on Kagi is from ErgoDox’s Indiegogo in 2015.
They may have coined the term.
Ah, sorry. I was answering about hyper.
The earliest reference to “meh key” I’m turning up on Kagi is from ErgoDox’s Indiegogo in 2015.
They may have coined the term.
That would be the Space-cadet
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).
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.
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.
Radarr and Sonarr both have features to sym/hardlink files to new places after the download client tells them it’s finished.
Filebot also gets mentioned a lot for this task, though I haven’t used it.