- Top Pick: KYY Portable Monitor 15.6-inch 1080P
- Runner-up: Anker 7-Port USB 3.0 Powered Hub
- Also consider: 8BitDo Ultimate 2 Bluetooth Controller
One gaming PC, two players, each with a personal screen, controller, and headset, playing at the same time. On Linux this is not a streaming trick or a split-screen compromise. The operating system has a formal concept for it, the seat, and systemd-logind has managed seats for years: a bundle of hardware (a graphics device, a display, input devices, audio) assigned to one user session and isolated from every other session. A single tower, configured this way, behaves like two modest gaming PCs sharing a case and a power supply.
This guide is the two-seat blueprint: how the seat model works, the two routes to building the second seat, how graphics and USB devices get assigned, and where the honest limits sit. It is not couch co-op on one shared screen, nor the single-player GPU passthrough guide; multiseat is its own discipline.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Yes: Linux can run two independent gaming seats on one PC. systemd-logind assigns a graphics card, display, and USB devices to each seat, so two players get separate sessions on one machine. You need a graphics device per seat natively, or one GPU passed through to a virtual machine for the second seat, plus separate game accounts for most online titles.
The seat model in plain terms
Every Linux desktop session already runs on a seat. The default seat is called seat0, and it owns the hardware never explicitly assigned anywhere: the main graphics card, the keyboard and mouse plugged in first, the onboard audio. A multiseat setup simply creates a second seat, seat-1, and attaches specific devices to it. From that moment, logind treats those devices as belonging to the second seat only. Its display shows its own login screen, its session gets its own input stream, and its user cannot see or touch the first seat’s hardware.
Assignment happens through loginctl: the attach command binds a device, identified by its sysfs path, to a named seat, persistently, as a udev-level property of the device. Attach a graphics card and a USB hub to seat-1 and the second station has its skeleton: everything on that hub arrives in the second session and nowhere else.
Two requirements shape everything else. A seat needs its own graphics device; there is no seat without a display path. And it needs a display manager that understands multiseat, which mainstream options such as GDM do, starting a separate greeter and session per seat once the assignment exists.
Two routes to the second seat
The native route runs two ordinary desktop sessions side by side. Seat0 keeps the primary graphics card and the host desktop. Seat-1 gets a second graphics device, a modest discrete card or, on many processors, the integrated GPU. Each player logs in, launches Steam, and plays as if the other seat were not there. This route is simple, has no virtualization overhead, and keeps both players on the same kernel and driver stack. Its price is rigidity: the hardware split is fixed, and both seats share one CPU, memory pool, and storage stack, so two demanding games divide the machine between them.
The virtual machine route keeps one native seat and builds the second seat inside a VM. The guest receives a whole graphics card through VFIO passthrough, plus its own USB controller or assigned hub, its own display output, and its own audio device. This route costs more configuration: IOMMU groups constrain which devices can be handed over together, and the guest’s share of CPU and RAM is reserved rather than borrowed. In return it isolates the second player completely: the guest can run a different operating system, and a crash or reboot inside it never touches the host seat.
GPU and display assignment
Graphics hardware is the binding constraint, so plan it first. In the native route, logind assigns a whole DRM graphics device to a seat. One graphics card with two monitors attached is still one device: both screens belong to the same seat, which is a dual-monitor desk, not two seats. Two seats natively means two graphics devices, and the classic budget build pairs a discrete card for one seat with the processor’s integrated graphics for the other. Check first that the integrated GPU can stay enabled alongside the discrete card in firmware settings, because some boards disable it by default.
In the VM route the same rule appears in different clothes: the host keeps a graphics device, the guest takes the passed-through card and its display outputs, and that card cannot be shared back while the VM runs. Each seat’s display should be a real, separate screen cabled to its own graphics output; a portable monitor on the second seat’s output is a legitimate space-saving choice.
Input and audio isolation
Input isolation is where the hub trick earns its keep. Assigning input devices one by one is tedious and brittle, because a replaced mouse arrives as a new device. Assigning a whole USB hub or controller to seat-1 is cleaner: logind binds the upstream device, and everything downstream of it belongs to that seat permanently. Seat two’s keyboard, mouse, controller dongle, and headset all live on that hub, and none of their input reaches seat0’s session. Controllers behave the same way; a gamepad on seat-1’s hub is visible only to seat-1’s Steam, so two players can run the same game independently without input cross-talk.
Audio follows the same per-seat logic. A session can only use audio devices attached to its seat, so onboard sound stays with seat0 and the second seat needs a sound device of its own. The inexpensive answer is a USB audio adapter on seat-1’s hub: USB audio class devices need no special driver, appear as that seat’s headset and microphone, and keep voice chat fully separate.
The licence reality: two players, two libraries
Hardware is only half the build. To most games and launchers, the second seat is simply a second computer. One Steam account cannot be playing in two places at once, so two players means two accounts. Family sharing does not dissolve this: a shared library can only be in use by one person at a time, so simultaneous play needs its own licences, and two copies of the same online game if both players want it at once.
There are friendly exceptions. DRM-free games, GOG releases being the common example, generally run wherever they are installed, and LAN-oriented titles are built for exactly this kind of household duplication. Budget the second seat’s library as part of the build; for many households the second set of licences costs more than the second set of hardware.
How to choose
Choose the native route when the machine has two usable graphics devices, typically a discrete card plus integrated graphics, and both seats run Linux: it is simpler to build, and neither player pays a virtualization tax. Choose the VM route when one seat must stay untouched as the household’s main PC, when the second seat might run a different operating system, or when its resources should be fenced off so a guest crash or reboot cannot disturb the first player. With only one graphics device and no integrated GPU, neither route works; that purchase comes first.
Who should skip this
Skip multiseat if both players mostly play the same competitive online titles at once and expect one modest PC to carry both at full quality; the shared CPU and storage are the ceiling, and two mid-range machines serve that household better. Skip it if your games depend on kernel-level anti-cheat that already refuses Linux or virtual machines, because a second seat changes nothing there. And skip it if the second player only occasionally joins for shared-screen co-op, which needs no seat at all.
The second-seat kit
Beyond the second graphics device, a seat needs a screen, one assignable hub, and per-seat input and audio. These five pieces are the standard shopping list.
KYY Portable Monitor 15.6-inch 1080P
A portable panel is the pragmatic second display: it takes a Mini-HDMI or USB-C feed from the second seat’s graphics output and folds away when the seat is idle.
Specs:
- 15.6-inch IPS panel, 1920 x 1080, 60 Hz
- Inputs: two full-function USB-C ports and Mini-HDMI
- Built-in stereo speakers and 3.5 mm audio jack
- Smart cover that doubles as a stand
Anker 7-Port USB 3.0 Powered Hub
This hub is the seat boundary: attach it to seat-1 and every keyboard, mouse, dongle, and headset plugged into it belongs to the second seat, permanently.
Specs:
- Model AK-68ANHUB-BV7A-0004
- Seven USB 3.0 data ports
- 36W power adapter included for reliable bus power
- One BC 1.2 charging port
8BitDo Ultimate 2 Bluetooth Controller
Seat two’s gamepad: its 2.4G dongle sits on seat-1’s hub, so the pad pairs to that seat only, never to the first player’s session.
Specs:
- Model 80ND
- Bluetooth, 2.4G wireless, and wired USB modes
- TMR joysticks and switchable trigger modes
- 1000 mAh battery with charging dock included
Sabrent USB External Stereo Sound Adapter (AU-MMSA)
The second seat’s sound card: one adapter on the assigned hub gives it a headset output and microphone input of its own, independent of seat0’s onboard audio.
Specs:
- Model AU-MMSA
- USB Audio Class device, plug and play with no drivers to install
- 3.5 mm stereo headphone output and microphone input
- Aluminum housing
Logitech MK270 Wireless Keyboard and Mouse Combo
One nano receiver is one device to assign, which is exactly what a seat wants: keyboard and mouse arrive through a single USB device on seat-1’s hub.
Specs:
- Model 920-008813
- 2.4 GHz wireless with a single USB nano receiver
- Full-size keyboard with eight multimedia and shortcut keys
- Compact ambidextrous mouse
FAQ
Can one graphics card drive two seats?
Not in the native logind model: a seat is built around its own graphics device, so one card with two monitors makes one dual-screen seat. Two seats need two graphics devices, or a second card passed through to a virtual machine.
Do both players need to buy the same game twice?
Usually, yes, for simultaneous play. Each seat behaves as a separate computer with its own account, and a shared library can only be in use by one person at a time. DRM-free releases and LAN-focused titles are the main exceptions.
What happens when one seat reboots or crashes?
In the native route both sessions share one kernel, so a system crash takes both seats down, though one player’s game crashing leaves the other seat alone. In the VM route the guest can reboot or crash without disturbing the host seat.
Is a second seat good for competitive online play?
It works, with shared limits. Both seats share the CPU, storage, and internet connection, and titles whose anti-cheat refuses Linux or virtual machines stay refused. For two simultaneous demanding matches, separate machines remain the stronger answer.
Final verdict
Multiseat is the most underused trick in Linux gaming: the seat model is built into the system, the assignment is a handful of loginctl commands, and a second graphics device plus a hub, a screen, and per-seat audio turns one tower into two honest gaming stations. Build natively when two graphics devices fit the household; build the second seat as a VM when isolation matters more than simplicity. Plan for the real costs: a graphics device per seat and a second library of licences.











