LookingGlass
vendor-reset
Our great sponsors
LookingGlass | vendor-reset | |
---|---|---|
24 | 143 | |
4,479 | 701 | |
- | - | |
9.5 | 0.0 | |
10 days ago | 11 days ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LookingGlass
-
VirGL
Unfortunately AMD cards suffer from a reset bug, still.
The reset bug being that you can pass through the card fine, once. But if you try to pass it through again (or the card experiences an issue and needs to reset), they get caught in some kind of bad state and won’t work until power is removed and restored. Which requires a reboot or a only slightly less disruptive dance with system power states.
For vega and 5000 series gpu’s, there’s https://github.com/gnif/vendor-reset
Incidentally, nvidia gpus are so good at resetting, they’ve probably done so without you noticing. If the screen ever goes black for a fraction of a second and returns in normal usage, it was probably because it reset itself.
The lower 6000 series lower than the 6800’s for example may or may not have the issue. It seems most “reference” cards are fine, but custom vendor cards often but not always have issues. My reference 6700 works fine, but a sapphire 6700 probably won’t.
And the 7000 series is also fucky in a new way somehow. Gnif knows far more about this than me, and has basically thrown up his hands at how AMD doesn’t care. He’s made occasional posts about it on https://forum.level1techs.com/
Gnif is also responsible for Looking glass: https://github.com/gnif/LookingGlass
-
Virtual Machine stinkyness
You could try LookingGlass. That may require two GPUs.
-
scrcpy 2.0 is released, with audio support!
It's a pair of apps, one runs on a Windows virtual machine, the other on the host OS, that uses shared memory to copy a passed-through GPUs frame buffer. Runs fast enough to get 4k/120fps very low latency, so if you have a spare GPU you can game on it in Windows, from a Linux desktop. https://github.com/gnif/LookingGlass
-
Can you make a passed through GPU display to a emulated display in virt-manager?
Check out https://github.com/gnif/LookingGlass if you can accept a separate window.
-
looking glass doesn't detect my mouse
then everything looks normal. It's all up to EGL though, as looking-glass really doesn't have any code that handles image scaling (see here).
- Looking glass B6 released!
- AMD RX580 passthrough with looking glass doesn't work
-
The Death of the PCIe Expansion Card
https://github.com/Arc-Compute/LibVF.IO/tree/master/ plus https://github.com/gnif/LookingGlass works pretty well. If you use an Intel GPU, particularly one of their new Arc dedicated GPUs, it supports the functionality on the consumer grade hardware without any trickery and you just need Looking Glass to map the outputs.
-
Passing audio from 1 VM to another for final mixing?
I'd like to introduce you to Looking Glass as a much higher quality and lower latency alternative to NDI when you are trying to relay frames between virtual machines within the same computer. With a patched nvidia driver to enable nvfbc on the gaming VM there is almost zero performance penalty when capturing gameplay. It also has options for audio, which I don't use because they didn't exist when I was configuring my system. I have a similar use case (gaming and streaming) and hardware (5950X + two gpus). I am not using proxmox, however. My configuration using QEMU and libvirt has this XML:
-
Looking Glass Beta 5 Released!
What stopping from tagging a stable release? The milestone has no open issues.
vendor-reset
-
Problems with single GPU passthrough | AMD 5700 XT
I have the vendor-reset fix. I have disabled resizable bar, and I have added the fix for the AMD driver detecting the VM in the XML file.
-
Windows 11 VM not shutting down fully
Credit to the fine people in this github issue:https://github.com/gnif/vendor-reset/issues/46
-
VirGL
I’m not sure what you mean by forwarding, but if you mean regular gpu passthrough and the reset bugs with amd gpus, then for the rx580 vendor-reset should typically work: https://github.com/gnif/vendor-reset
Does not work with the lower 6000 (below 6800) and 7000 series that can also have reset issues.
- Supported methods of using DKMS kernel modules; GPGPU virtualization
- swtpm_setup: Not overwriting existing state file.
- Worried about vbios size and hash (single gpu passthrough).
-
AMD GPU Passthrough Black Screen on VM Boot
Just an update installing vendor-reset to counteract the amd gpu reset bug fixed my issues completely. Are you running an amd gpu by chance, it may be worth a shot to try it. https://github.com/gnif/vendor-reset
-
[HELP] AMD REST BUG
1) download https://github.com/gnif/vendor-reset/archive/refs/tags/v0.1.0.zip
- Did anyone using windows 10 VM with an AMD GPU have issues installing the proprietary drivers in windows? Win 10 VM just gets BSOD once they start installing
- GPU Passthrough errors: BAR 0, Error 43, vendor-reset
What are some alternatives?
OSX-KVM - Run macOS on QEMU/KVM. With OpenCore + Monterey + Ventura + Sonoma support now! Only commercial (paid) support is available now to avoid spammy issues. No Mac system is required.
vfio-single-amdgpu-passthrough - This repo is a tutorial for single amd gpu passthrough to various qemu VMs
kvm-guest-drivers-windows - Windows paravirtualized drivers for QEMU\KVM
single-gpu-passthrough
barrier - Open-source KVM software
Single-GPU-Passthrough
Magpie - An all-purpose window upscaler for Windows 10/11.
sndcpy - Android audio forwarding (scrcpy, but for audio)
KVM-Opencore - OpenCore disk image for running macOS VMs on Proxmox/QEMU
QtScrcpy - Android real-time display control software
vfio