Please provide the host log, without it there is nothing we can do.
i just remembered i had this issue before, im wondering if you have tried this, its an issue with the kvm spice acting as the primary display.
try adding this
https://forum.level1techs.com/t/psa-lookingglass-with-clipboard-support-and-libvirt-without-qxl/139539
<video>
<model type='none'/>
</video>
if that doesnt work, im wondering if you had the same issue where windows defender prevented it from running, check that and see if it helps
I added that, thank you. Unfortunately I still only get the keyboard passing through from the client to the host, video is not coming from the host to the client.
I think Windows Defender (or something) is not allowing the looking-glass-host.exe to run in my Windows 10 VM. I hope Iām not crazy in expecting to see ālooking-glass-hostā in either the Processes or Details tab in Task Manager, right?
Everything looks like it should be running at startup but Iām not convinced. With a few changes, I finally got the looking-glass-client to timeout when trying to connect to the spice server.
Any other thoughts?
1 Like
Yes, it should be there when it is running, also the LG icon should appear on the tray icon.
Check the windows event log to see if there is any errors related to launching it, also please look for the log that LG produces and provide it. It will be at C:\Users\YourUser\AppData\Local\Temp\looking-glass-host.txt
Thank you for that, I have seen the tray icon flash a few times when I was looking for it. Log file shows āUnable to enumerate the device, is it attached?: 0x00000103 (No more data is available.)ā.
I found a potential solution by installing the patched driver noted here:
"Edit:
Solved the problem for windows host. Forget that needed to install the patched IVSHMEM Driver on windows side from https://github.com/virtio-win/kvm-guest-drivers-windows/issues/217 "
Only thing is that is from 2017 and there were specific notes to install the latest driver 0.1-161 or later, which I have. So I fear Iām in a slightly different situation.
I show the āVirtIO Balloon Driverā as installed in the Windows 10 VM. Any way to see if itās working correctly?
There is no āpatchedā IVSHMEM Driver, it simply is THE driver.
Nothing has changed in the IVSHEMEM driver since, youāre still good.
Not the place to ask this sorry.
Again, thank you to all that have posted things to try. The IVSHMEM driver wasnāt extracted correctly in my VM, once I did that, I was able to get it to actually install.
All is working now. Looking Glass and all of you are awesome.
My VM will play audio up until I connect the looking-glass-client, at that point I lose audio within the VM and via the looking-glass-client. If I reboot the VM, it will have audio until I connect the looking-glass-client again. Any suggestions?
Are you using Scream over IVSHMEM?
Finally able to get back to thisā¦
No I have not setup Scream for IVSHMEM.
Is that required?
It is not required. What r you using to listen to audio on your VM?
Just the onboard audio. Works until lookingglass connects.
oh. the VM spice host will only allow one connection and this connection, by default, carries your audio.
so when you start the lg-client with spice (the -s switch)ā¦
the previous connection also states to be broken (like in virt-manager)? looking-glass-client has no audio stackā¦
you can change that, see option 2 in http://mathiashueber.com/virtual-machine-audio-setup-get-pulse-audio-working/ for example
Again, I just want to say thank you to everyone that has given me help through this. Iāve gotten my system working to a point Iām OK with, not perfect but it works.
1 Like
how much of a performance hit is there when capturing with the looking glass.exe on windows. with obs i recorded task manager and it was using up to 40% gpu when playing teamfortress 2. im running a 1080ti, 40% seems very high.
What resoltuion? What framerate? Do you have v-sync enabled in the game?
Hi, I am trying to get this awesome application following the guide (I am using Debian indeed) but, when I try running compiled Beta 1 client, I get:
asvhen@negro:~/Descargas/LookingGlass-master$ ./client/build/looking-glass-client -s
[I] main.c:996 | run | Looking Glass (B1-rc6-6-gb979752989+1)
[I] main.c:997 | run | Locking Method: Atomic
[I] egl.c:187 | egl_initialize | Double buffering is on
[I] egl.c:201 | egl_initialize | Multsampling enabled, max samples: 4
[I] main.c:902 | try_renderer | Using Renderer: EGL
[I] main.c:1183 | run | Using Clipboard: X11
[I] main.c:1259 | run | Waiting for host to signal itās readyā¦
[E] crash.linux.c:172 | crit_err_hdlr | ==== FATAL CRASH (B1-rc6-6-gb979752989+1) ====
[E] crash.linux.c:173 | crit_err_hdlr | signal 11 (Segmentation fault), address is 0x720
[E] crash.linux.c:201 | crit_err_hdlr | [trace]: (0) /lib/x86_64-linux-gnu/libGL.so.1(+0xd6ae9) [0x7f48fc6a4ae9]
2560x1440, 165hrtz, no v-sync
Although I am only displaying it at
1920x1080, 75hrtz on the linux machine
Helpful tip: Always include current Debian version and kernel version. Please post the output of the following command:
uname -a && lsb_release -a
Also, do a dpkg -l libgl1 and post the output of that, too. This makes it much easier to help! 
Of course:
uname -a && lsb_release -a
Linux negro 4.19.37 #1 SMP Sun Jul 21 12:34:23 CEST 2019 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux bullseye/sid
Release: testing
Codename: bullseye
dpkg -l libgl1
Deseado=desconocido(U)/Instalar/eliminaR/Purgar/retener(H)
| Estado=No/Inst/ficheros-Conf/desempaqUetado/medio-conF/medio-inst(H)/espera-disparo(W)/pendienTe-disparo
|/ Err?=(ninguno)/requiere-Reinst (Estado,Err: mayĆŗsc.=malo)
||/ Nombre VersiĆ³n Arquitectura DescripciĆ³n
++Ā±==============-============-============-=======================================================
ii libgl1:amd64 1.1.0-1 amd64 Vendor neutral GL dispatch library ā legacy GL support
ii libgl1:i386 1.1.0-1 i386 Vendor neutral GL dispatch library ā legacy GL support