Changes
Jump to navigation
Jump to search
For libvirt versions before 5.10.0, if you are using AppArmor, you need to add permissions for QEMU to access the shared memory socket. This can be done by adding <code>/dev/shm/looking-glass rw,</code> to the ''/etc/apparmor.d/abstractions/libvirt-qemu'' file.
typo
</syntaxhighlight >
===== Arch Linux / Manjaro =====
<syntaxhighlight lang=bash>
First set up the necessary USE flags if needed:
<syntaxhighlight lang=bash>
echo "media-libs/libsdl2 glesgles2" >> /etc/portage/package.use/libsdl2
echo "media-libs/nettle gmp" >> /etc/portage/package.use/nettle
</syntaxhighlight>
</syntaxhighlight>
;NOTE: The most common compile error is related to backtrace support this . This can be disabled by adding the following option to the cmake command. : '''-DENABLE_BACKTRACE=0''', however, if you disable this and need support for a crash please be sure to use gdb to obtain a backtrace manually or there is nothing that can be done to help you.
Should this all go well you should be left with the file '''looking-glass-client'''. Before you run the client you will first need to configure either Libvirt or Qemu (whichever you prefer) and then set up the Windows side service.
The memory size (show as 32 in the example above may need to be adjusted as per [[Installation#Determining_Memory|Determining Memory]] section.
If you would like to use Spice to give you keyboard and mouse input along with clipboard sync support be sure to also do the following:
If you want clipboard synchronization please see [[FAQ#How to enable clipboard synchronization via SPICE]]
==== AppArmor ====
For libvirt versions before '''5.10.0''', if you are using AppArmor, you need to add permissions for QEMU to access the shared memory file. This can be done by adding the following to ''/etc/apparmor.d/abstractions/libvirt-qemu''.
/dev/shm/looking-glass rw,
=== Qemu Commands ===
'''French:''' "Gestionnaire de périphérique" -> "Périphériques Système" -> "Contrôleur de RAM Standard PCI"
'''English:''' "Device Manager" -> "System Devices" -> "PCI standard RAM Controller"
A signed Windows 10 driver can be obtained from Red Hat for this device from the below address:
Using IVSHMEM with Scream may interfere with Looking Glass as it may try to use the same device. Please do not use the IVSHMEM plugin for Scream. Use the default network transfer method. The IVSHMEM method induces additional latency that is built into its implementation. When using VirtIO for a network device the VM is already using a highly optimized memory copy anyway so there is no need to make another one.
If you insist on using IVSHMEM for Scream despite it's its inferiority to the default network implementation the Windows Host Application can be told what device to use. Create a looking-glass-host.ini file in the same directory as the looking-glass-host.exe file. In it, you can use the os:shmDevice option like so:
<syntaxhighlight lang=INI>
The windows host application captures the windows desktop and stuffs the frames into the shared memory via the shared memory virtual device, without this Looking Glass will not function. It is critical that the version of the host application matches the version of the client application, as differing versions can be, and usually are, incompatible.
'''Note:''' As of 2020-08-12 (commit dc4d1d49fac2361e60c9bb440bc88ce05f6c1cbd), the below instructions are deprecated. The host application now has an installer that installs a system-wide service to run the Looking Glass host application. When upgrading please be sure to remove the scheduled task if you have already created one.
To get the Windows-Host-Application running after restart you need to run it as a privileged task we do that by starting '''cmd.exe''' as '''administrator''' and running a command in it which creates a windows task.
https://github.com/gnif/LookingGlass/blob/master/client/README.md
Common options include '-s' for disabling spice, '-S' for disabling the screen saver, and '-F' to automatically enter full screen and '-k' to disable the UPS/FPS rate.
