gitwtfhub

wtf is edge-desktop-virtualization?

open-edge-platform/edge-desktop-virtualization — explained in plain English

Analysis updated 2026-08-08 · repo last pushed 2026-08-03

5StarlarkAudience · ops devopsComplexity · 4/5ActiveSetup · hard

TL;DR

Splits one Intel GPU across multiple virtual desktops on a single machine using SR-IOV, letting several people run graphics-heavy apps from one workstation via Kubernetes.

Mindmap

mindmap
  root((repo))
    What it does
      Splits Intel GPU
      Multiple virtual desktops
      High performance isolation
    Tech stack
      Starlark
      Kubernetes
      Kubevirt
      Helm charts
    Use cases
      Factory floor stations
      Virtual desktop infrastructure
      Multi-user remote desktops
    Hardware needs
      Intel 12th Gen or newer
      64GB RAM recommended
      500GB SSD storage
    How it works
      SR-IOV GPU partitioning
      Intel device plugin
      Bootable disk images
    Audience
      Edge infrastructure teams
      Cloud desktop providers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Serve multiple operator displays from a single factory floor PC.

REASON 2

Offer virtual desktops to employees without buying a separate computer for each person.

REASON 3

Run multiple graphics-heavy remote desktops from one Intel-GPU workstation.

REASON 4

Deploy Windows or Ubuntu guest VMs on Kubernetes with dedicated GPU slices.

What's in the stack?

StarlarkKubernetesKubevirtHelmIntel SR-IOV

How it stacks up

open-edge-platform/edge-desktop-virtualizationcodeitlikemiley/bossgoogle/cel-spec
Stars53,798
LanguageStarlarkStarlarkStarlark
Last pushed2026-08-032025-08-11
MaintenanceActiveQuiet
Setup difficultyhardhardhard
Complexity4/53/54/5
Audienceops devopsdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1day+

Requires Intel 12th Gen+ CPU, SR-IOV enabled in BIOS, Kubernetes with Kubevirt, and recommended 64GB RAM plus 500GB SSD.

No license information was provided in the repository explanation.

Wtf does this do

Edge Desktop Virtualization lets you take a single computer with an Intel GPU and split that graphics hardware among multiple virtual desktops running on the same machine. The main benefit is that each virtual machine gets its own dedicated slice of the GPU, so several people can run graphics-heavy applications simultaneously from one physical box, think of it as turning one workstation into several high-performance remote desktops. Under the hood, it uses an Intel technology called SR-IOV, which is a standard for dividing a single physical device into multiple virtual ones. The host operating system manages the full GPU, then carves out isolated virtual "slices" that each virtual machine accesses directly. Because each VM talks to its own slice without going through a software middleman, performance stays high and latency stays low, important for things like video playback, media processing, or any graphics-intensive workload. The project bundles the tools needed to run all of this on Kubernetes-based infrastructure. It includes setup steps for enabling SR-IOV on the host machine, installing Kubernetes along with Kubevirt (a tool for running VMs inside Kubernetes), and an Intel device plugin so the cluster knows how to hand out GPU slices to virtual machines. The README also walks through creating bootable disk images for Windows or Ubuntu guest VMs and deploying them using provided Helm charts. Helm is a package manager for Kubernetes that simplifies deploying applications. The intended users are organizations building edge or cloud desktop infrastructure, for example, a factory floor station serving multiple operator displays from one PC, or a business offering virtual desktops to employees without buying a separate computer for each person. It requires Intel 12th Gen Core processors or newer, with a recommendation of 64GB of RAM and at least 500GB of SSD storage, so this is aimed at fairly capable hardware setups rather than lightweight machines.

Yoink these prompts

Prompt 1
Set up SR-IOV on an Intel 12th Gen host and deploy a Kubernetes cluster with Kubevirt so I can split one Intel GPU across multiple virtual desktops.
Prompt 2
Create a bootable Ubuntu disk image and deploy it as a GPU-backed virtual machine using the Helm charts from this repository.
Prompt 3
Install the Intel device plugin on my Kubernetes cluster and assign dedicated GPU slices to Kubevirt virtual machines.
Prompt 4
Walk me through enabling SR-IOV on my Intel GPU host and verifying that each virtual machine gets its own isolated GPU slice.
Prompt 5
Deploy multiple Windows guest VMs on a single Intel-GPU workstation using this repo's Helm charts so several users get high-performance remote desktops.

Frequently asked questions

wtf is edge-desktop-virtualization?

Splits one Intel GPU across multiple virtual desktops on a single machine using SR-IOV, letting several people run graphics-heavy apps from one workstation via Kubernetes.

What language is edge-desktop-virtualization written in?

Mainly Starlark. The stack also includes Starlark, Kubernetes, Kubevirt.

Is edge-desktop-virtualization actively maintained?

Active — commit in last 30 days (last push 2026-08-03).

What license does edge-desktop-virtualization use?

No license information was provided in the repository explanation.

How hard is edge-desktop-virtualization to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is edge-desktop-virtualization for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.