HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
DualCoder
vgpu_unlock
C2021–2024
DualCoder / vgpu_unlock

vgpu_unlock

Unlock vGPU functionality for consumer grade GPUs.

16Distinct people
18Mentions
0Explicit recommenders
5.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Unlock vGPU functionality for consumer grade GPUs.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2021-04-09 18:42:05 UTC to 2024-06-06 10:33:53 UTC.

0369122021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC11110
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303

What Hacker News says

18 sources
Hardware segmentation in general is just pretty unfortunate. Another example I saw mentioned recently was in-band ECC - Intel’s memory controller apparently supports this but is only enabled in some limited scenarios [0]. If I could enable in-band ECC on my workstation I absolutely would. Given that some folks did manage to unlock the VGPU functionality on consumer GPUs [1] the silicon is certainly capable, but I guess Nvidia doesn’t want to cannibalise their data centre sales. [0] - https://edc.intel.com/content/www/us/en/design/ipla/software... [1] - https://github.com/DualCoder/vgpu_unlock
In QEMU Hardware accelerated h264/h265 video encoding added to VirGL
I'm glad Intel has been swallowing their pride on this one, I want them to succeed for once. What really would drive me to support them directly would be (para)virtualization support via SR-IOV/GVT-g. Especially given Microsoft's recent stunts an increasing amount of people (including me and close friends) are evaluating moving to Linux while keeping a Windows VM around, but both NVIDIA and AMD seem adamant about keeping those features gated to enterprise cards (even thought it's a software thing, see community efforts to reverse this[1]) so they can charge ludicrous prices to businesses for those. My opinion is that if Intel wants to get their foot in the door they should win over enthusiast by breaking patterns such as this one rather than try to compete exclusively on performance. [1]: https://github.com/DualCoder/vgpu_unlock
In LTT showcases A770 with some performance data, price estimate [video]
> Is that done at the driver level? No, the FP64 units aren't physically present on silicon in high numbers on the non xx100 dies. However, limitations enforced just by the driver and its FW set: - GPU virtualisation (see: https://github.com/DualCoder/vgpu_unlock) - NVENC video encoder limitations to 2 simultaneous streams on customer cards - Lite Hash Rate limitation enforcement to make GPUs less attractive for miners
In “With those changes we're up to a 94% pass rate for dEQP-GLES2”
I use https://github.com/danielfullmer/nixos-nvidia-vgpu + https://looking-glass.io/ very successfully Can theoretically game on Linux and windows at same time with just a single gpu (2080 ti), mainly use it cause I only have single gpu and I don't want to loose hardware acceleration on Linux, the nixos module both applies a the vgpu unlocker for consumer graphic cards (so u can split a gpu in multiple virtual gpus) https://github.com/DualCoder/vgpu_unlock And merges it with the GeForce drivers so the host gpu does not stop having display output And I just passthrough the vgpu and Xbox controllers to the vm with qemu and my main windows nvme disk (windows naturally just works inside and outside a vm for me, dual boot)
In Nix-GUI: Make NixOS usable for non-technical users through settings / GUI
It depends on your internal GPU. If it's an Intel GPU, you could use vfio-mdev, which allows you to split your physical GPU into smaller counterparts. It will only work with the macOS version that are compatible with Intel GPUs (probably most of them). Have a look here for a guide on Archlinux : https://wiki.archlinux.org/title/Intel_GVT-g. And here for a script to deploy macOS on KVM : https://github.com/kholia/OSX-KVM. Side-note : vfio-mdev can now be unlocked on consumer-grades Nvidia cards too : https://github.com/DualCoder/vgpu_unlock. Sadly, it is not possible for AMD-cards. By the way, I am working on Phyllome OS (https://phyllo.me/), which is an attempt to make it easier to do such things. But please don't tell anyone :)
In Looking Glass: Run a Windows VM on Linux in a window with native performance
Perhaps, but the standard VFIO-style passthrough methods (if you can call anything about that "standard") is still a terrible solution; it requires more than one GPU to use both systems at once, requires navigating horrifically underdocumented driver systems that brick the system when experimented with (just like everything in Linux does, for that matter), and requires at the very least switching inputs between the host and the guest even if all of that works perfectly somehow. Sure, there might not be any more Code 43 (which wasn't the hardest thing to bypass, but you did have to hide the fact that the VM was a VM), but Code 43 was the relative tip of the iceberg compared to all the other setup you had to do to even get there in the first place. Passing through an nVidia GPU the way that data centers do it, where you can run several hard
Read the rest
ware-accelerated VMs on the same GPU (as well as the host, on only one set of outputs), to my knowledge still requires this hack (https://github.com/DualCoder/vgpu_unlock); this is specifically what I'm referring to and is really the only workable solution as it's the closest to "press button get seamless performance from your gaming Windows VM" as we can get right now. I'd be delighted to now be wrong about my assessment of how difficult trying to set that nonsense up was, because then I could do it and stop worrying about how awful the Windows 11 experience is going to be (even GNOME, for all its user-hostility, still isn't stupid enough to ditch the taskbar labels for the full OS X dock; Windows 11 has so far made that shit mandatory).
In State of the Windows: How many layers of UI inconsistencies are in Windows 10?

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.