Changes
Jump to navigation
Jump to search
If you use AppArmor (which is enabled by default on Ubuntu), you will also need to add permission for qemu to access the memory file in apparmor. This can be done by adding '/dev/shm/looking-glass rw,' to the /etc/apparmor.d/abstractions/libvirt-qemu file
</syntaxhighlight >
===== Arch Linux / Manjaro =====
<syntaxhighlight lang=bash>
</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" -> "Standard PCI 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>
