7 ms·
This works well for the most part. However, there are some things worth considering. For one, the frame relay program will need to start in your guest before L
by jchw 7y ago
This works well for the most part. However, there are some things worth considering.
For one, the frame relay program will need to start in your guest before Looking Glass can connect. Last I checked the best you can do is have it start at login, so you need autologin to have a somewhat seamless setup.
Secondly, the cursor is sent through using the SPICE protocol, which is convenient. Unfortunately Looking Glass has no support for also handling audio, and no intent to merge such functionality in the future. So if you want audio, you’ll have to set up Qemu to forward audio directly to the host.
Finally, GPU passthrough setups is the thing that sold me on NixOS. If you’re a fairly experienced Linux user, setting up this complicated and multifaceted setup in a mostly reproducible way using a single file of configuration is pretty pleasing. Most of my configuration was this:
https://gist.github.com/jchv/b0e4b39679e450536a17cc6a5d69169a https://gist.github.com/jchv/b0e4b39679e450536a17cc6a5d69169...
Really, all you need is to substitute the right IDs and it should practically work anywhere, all you have to do is setup a VM with the requirements met (UEFI, PCI-e device passthrough, Looking Glass device attached, and KVM FR server running) and run Looking Glass.
Ultimately, I dropped Looking Glass and GPU passthrough. It was a little cumbersome and performance wasn’t perfect. I ran GPU passthrough on a physical monitor for a little while, and then dropped it entirely after finding out that Steam Proton and Wine actually covered all of my bases anyways.
- tbenst 7y agoHuh, cool! I’d love to run Illustrator/Photoshop on my NixOS box. I presume you use looking-glass-client from nixpkgs. Any other parts of the config you can share/recommend?
- jchw 7y agoNot that I can recall! Yeah, I was using that one. In fact, when I wanted to upgrade, I actually submitted PRs to Nixpkgs for it. In the meantime, though, you can of course just use overlays or overrides to get a more up to date looking-glass-client in your local setup. Now, that does actually bring up at least one nice bit of configuration, which is how to configure your overlays to be consistent system-wide. It's covered on the wiki. I'll be honest, I still find overlays a little bit confusing, but I eventually got this setup working. It has a lot of advantages over other methods, my favorite of which is that all of my overlay stuff is consistent across the machine and stored in my Git-versioned NixOS configuration. You might already have this, but it's worth noting. https://nixos.wiki/wiki/Overlays#Using_nixpkgs.overlays_from_configuration.nix_as_.3Cnixpkgs-overlays.3E_in_your_NIX_PATH https://nixos.wiki/wiki/Overlays#Using_nixpkgs.overlays_from... Other than that and setting up the libvirt box, there wasn't really much else to it. I had it done in an hour or two. Pretty sure the only other NixOS configuration I had was setting my user to be in the `libvirtd` group.