Cloud gaming · Infrastructure · 2023 — now
Launching games on virtual machines, on demand
Oneplay streams PC games to phones, TVs and browsers from GPU servers. I work on the backend that turns “Play” into a running game: VM launch on KVM, hot disk swaps, launch-request queuing and internal security.
Visit oneplay.in- Client
- Oneplay — cloud gaming
- Role
- Senior Cloud Game Engineer, platform team
- Stack
- Python · KVM · Linux · Request queuing · Internal auth
Simplified architecture sketch
- KVMon-demand VM launch per session
- Hot swapgame disks attached without rebooting
- Queuedfair launch-request scheduling
Context
In cloud gaming, every press of “Play” claims expensive GPU hardware. Start too slowly and players leave; over-allocate and the cost runs away. Peak evenings bring more launch requests than free machines.
The challenge
- 01Start a game session on a fresh VM quickly and reliably.
- 02Get the right game onto the VM without copying or rebooting.
- 03Handle more launch requests than free capacity — fairly.
- 04Keep internal services locked down.
Approach
VM launch on KVM
Sessions run on KVM virtual machines that the backend launches and tracks through their life cycle.
Hot disk swap
Game disks are attached to running VMs on the fly, so a machine can switch games without a rebuild.
Launch queue
When capacity is short, launch requests wait in a queue and are dispatched in order as machines free up.
Internal security
Service-to-service calls and host access are authenticated and kept off the public network.
Result
- ✦Launch path that holds up at evening peaks instead of failing outright.
- ✦Hardware reused across games through disk swaps instead of per-game machines.
Team effort on a private codebase (self-hosted GitLab). Details in interviews.