https://linux-kvm.org/api.php?action=feedcontributions&feedformat=atom&user=PimKVM - User contributions [en]2026-05-02T10:21:12ZUser contributionsMediaWiki 1.39.5https://linux-kvm.org/index.php?title=HOWTO_VMGL&diff=3467HOWTO VMGL2011-01-12T09:39:59Z<p>Pim: vmgl homepage moved</p>
<hr />
<div>= VMGL =<br />
Most of these steps are covered in the README file in the vmgl tar ball<br />
<br />
Download VMGL from [http://sysweb.cs.toronto.edu/vmgl here]<br />
<br />
install libXaw, libXext, libjpeg, libXmu devel files for your distro. '''Warning:''' compile problems from missing libraries do not stop the Makefile and so keep an eye of out for them as the compile flies by.<br />
<br />
On 64-bit, I had to download and patch tightvnc with the patches provided in ''extra/patches/Xvnc.patch'' and ''extra/patches/vncviewer.patch'' as the provided code would not compile. Everything went smoothly on 32-bit (Ubuntu).<br />
<br />
The vmglext module for Xorg is not compiled, but comes as a 32-bit binary in the download. This will not work for 64-bit unless you patch Xorg.<br />
<br />
On the host, run '''make''' and '''make install-host''', on the guest run '''make''' and '''make install-guest'''. Requires sudo to install (if in a system path) and to change ldconfig to look for VMGL loadable modules.<br />
<br />
'''Warning: Usermode network stack cripples performance, use Tap for now.'''<br />
<br />
== Using VNC ==<br />
add<br />
<br />
Section "Module"<br />
Load "vmglext"<br />
EndSection<br />
<br />
to your ''/etc/X11/xorg.conf''<br />
<br />
Once you start kvm with the -vnc option, point your ''patched'' vncviewer to the appropriate display.<br />
<br />
When you start vncviewer you will see something in the output like this: ''Set GLSTUB var in guest to point to port 7001''<br />
<br />
If you don't see the above message (or vncviewer fails to start) you are probably using an unpatched vncviewer.<br />
<br />
In the guest then run: ''export GLSTUB=<host ip>:7001''<br />
<br />
As a test, running glxinfo and glxgears should work. The output of glxinfo should refer to the fact that it is using VMGL. If you seen an error like this ''CR Error(3458): Need to know glStub environment variable'', then you haven't set your GLSTUB environment variable properly.<br />
<br />
== Using X forwarding ==<br />
Login in to the guest from the host with ssh using either the -X or -Y options to allow X forwarding. <br />
<br />
'''On the guest:''' run the ''stub-daemon'' program and then look in the file ''~/.stub-daemon'' to find out what to set your GLSTUB environment variable to. <br />
<br />
'''On the host:''' Set the GLSTUB variable appropriately and then run glxinfo or glxgears to test. See the VNC section above if you encounter errors.<br />
<br />
== Using SDL ==<br />
<br />
Currently, the QEMU/KVM standard SDL viewer does not work with VMGL.</div>Pim