Changes
Jump to navigation
Jump to search
{{Start downloading the correct version for your release from https:Windows_Host_Application}}//looking-glass.hostfission.com/downloads. You can either choose between '''Official Releases''' which is is stable or '''Release Candidates''' that tries to be stable but has new features. '''Note:''' If your '''looking-glass-client''' was created by building from the '''master branch''' you have to pick the '''Bleeding Edge''' version. 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. 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.<syntaxhighlight lang=batch>SCHTASKS /Create /TN "Looking Glass" /SC ONLOGON /RL HIGHEST /TR C:\Users\<YourUserName>\<YourPath>\looking-glass-host.exe</syntaxhighlight> Copy the following command in to your cmd shell and replace the '''<YourUserName> ''' with your username '''(e.g. "games")''' and your '''<YourPath> ''' with the part where the looking-glass-host.exe is stored '''(e.g. "Documents")''' . [[File:Screenshot_cmd_windowstask.png|500px]] Now you simply need to hit enter in to the cmd shell and restart the vm to test if it worked.
<syntaxhighlight lang=bash>
zypper install make cmake binutils-devel libSDL2-devel libSDL2_ttf-devel libnettle-devel nettle spice-protocol-devel fontconfig-devel libX11-devel libconfig-devel libwayland-egl-devel libX11fixes-devel
</syntaxhighlight >
If you downloaded the file via the web link then you should have a 'zip' file. Simply unzip and cd into the new directory. If you used 'git' then cd into the 'LookingGlass' directory.
<pre stylesyntaxhighlight lang="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"bash>mkdir client/buildcd client/build
cmake ../
make
</presyntaxhighlight>
;NOTE: The most common compile error is related to backtrace support 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.
Add the following to the libvirt machine configuration inside the 'devices' section by running "virsh edit VM" where VM is the name of your virtual machine.
<pre stylesyntaxhighlight lang="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"xml>
<shmem name='looking-glass'>
<model type='ivshmem-plain'/>
<size unit='M'>32</size>
</shmem>
</presyntaxhighlight>
The memory size (show as 32 in the example above may need to be adjusted as per [[Installation#Determining_Memory|Determining Memory]] section.
=== Qemu Commands ===
----
'''If you are using virt manager then this does not apply to you.'''
Add the following to the commands to your QEMU command line, adjusting the bus to suit your particular configuration:
<pre stylesyntaxhighlight lang="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"bash>
-device ivshmem-plain,memdev=ivshmem,bus=pcie.0 \
-object memory-backend-file,id=ivshmem,share=on,mem-path=/dev/shm/looking-glass,size=32M
</presyntaxhighlight>
The memory size (show as 32 in the example above may need to be adjusted as per [[Installation#Determining_Memory|Determining Memory]] section.
You will need to adjust the memory size to a value that is suitable for your desired maximum resolution using the following formula:
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"code>
width x height x 4 x 2 = total bytes
total bytes / 1024 / 1024 = total megabytes + 2
</precode>
For example, for a resolution of 1920x1080 (1080p)
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"code>
1920 x 1080 x 4 x 2 = 16,588,800 bytes
16,588,800 / 1024 / 1024 = 15.82 MB + 2 = 17.82
</precode>
You must round this value up to the nearest power of two, which with the above example would be 32MB
=== Using the Windows Host Application ===
----
== Running the Client ==
