https://github.com/pgaskin/spicy-kvm

Almost like a KVM switch, but using SPICE, a virtual machine, and a dedicated GPU with a regular monitor connected to both machines.
https://github.com/pgaskin/spicy-kvm

ddc ddc-ci evdev kvm pipewire qemu-kvm udev

Last synced: 28 days ago
JSON representation

Almost like a KVM switch, but using SPICE, a virtual machine, and a dedicated GPU with a regular monitor connected to both machines.

• Host: GitHub
• URL: https://github.com/pgaskin/spicy-kvm
• Owner: pgaskin
• License: gpl-2.0
• Created: 2024-06-22T22:49:44.000Z (5 months ago)
• Default Branch: master
• Last Pushed: 2024-08-03T19:32:25.000Z (4 months ago)
• Last Synced: 2024-08-03T20:40:48.202Z (4 months ago)
• Topics: ddc, ddc-ci, evdev, kvm, pipewire, qemu-kvm, udev
• Language: C
• Homepage:
• Size: 54.7 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# spicy-kvm

> [!NOTE]

> This tool is still a work-in-progress, and I mostly made this for my own specific use case. The configuration is currently hard-coded, logging is racy, error messages may be obscure, and the code is somewhat messy. Some nice-to-have features are also missing. Everything more or less works (I've been using this since early 2024), but for now, you'll need to modify the code. I am not accepting pull requests.

Almost like a KVM switch, but using SPICE, a virtual machine, and a dedicated GPU with a regular monitor connected to both machines.

A tool to connect to GPU-passthrough virtual machines on the local network with a hotkey, forwarding input/audio over SPICE, and switching monitor outputs using DDC-CI.

It is designed for a very specific use case:

- You require low-latency audio/video/input for a virtual machine

  - Other remote desktop solutions like RealVNC or xfreerdp are simpler if you don't.

- The virtual machine is on the same host or the local network.

  - SPICE is TCP-based, and all input and audio is sent through it, so a bad network connection will result in severe performance issues.

  - Audio is low-latency if the network is, but it is not directly synchronized with the video output, so if both the video and audio aren't low-latency, they may end up out of sync.

- You are using GPU passthrough, and the machine is connected to a monitor (possibly the same one you're using for another machine -- you can use DDC-CI to automatically switch outputs).

- You want to pass raw input from a physical evdev input device to the virtual machine without physically disconnecting it and/or want to be able to switch using a hotkey.

- You want to use audio input/output from your client machine in the virtual machine simultaneously.

- You want to be able to still use your client machine remotely or on other screens with other input devices while accessing the virtual machine.

You can think about it like:

- Looking-glass, but for a VM on the local network.

- A poor-man's KVM switch and audio mixer.

- Moonlight/GameStream/virt-viewer, but with a real screen and lower latency.

If any of the above isn't true, you're better off:

- Using SPICE directly with virt-viewer for local or local network VMs.

- Using LookingGlass for local VMs with a dedicated GPU.

- Using Moonlight/GameStream for gaming on a remote computer (the input and audio latency will be higher, but it's still generally usable).

- Using RDP or VNC for general-purpose remote desktop access (RealVNC is very nice for remote desktop on Linux).

The audio buffering and device code is based on looking-glass.

```

dnf install cmake gcc g++ kernel-headers 'pkgconfig('{spice-protocol,samplerate,libpipewire-0.3,nettle,hogweed}')'

cmake -B build -DCMAKE_EXPORT_COMPILE_COMMANDS=1 -GNinja

ninja -C build

```

Ensure SPICE is enable and exposed over TCP. VirtIO input devices are also required.