"does not have GLX installed" is ambiguous.
If you mean:
"Can I use VirtualGL with a 2D X server/X proxy that does not have a GLX
extension?" Then yes, that is one of the fundamental purposes of
VirtualGL. Please refer to the documentation and the articles on
VirtualGL.org for more information about what the "2D X server" is, if
you don't already know.
If you mean:
"Can I use VirtualGL with a 3D X server that does not have a GLX
extension?" Then no, although we have an active feature request for
this:
https://github.com/VirtualGL/virtualgl/issues/10. The proposed
feature would interpose GLX calls and convert them into EGL calls, which
would eliminate the need for the 3D X server altogether, but this
feature would be extremely difficult and disruptive to implement without
multi-view Pbuffers, which don't currently exist in popular EGL
implementations.
If you mean:
"Can I use VirtualGL with a server that does not have OpenGL installed?"
Absolutely not. The purpose of VirtualGL is to perform server-side
OpenGL rendering with GPU acceleration and stream the rendered 3D images
over the network. So you can definitely use it with *client* machines
that lack OpenGL, but not *server* machines that lack OpenGL.
vglconnect (which enables the VGL Transport) is largely a legacy feature
meant to be used in conjunction with remote X (which is itself largely a
legacy feature.) In almost all cases, new users should be using
TurboVNC instead.
DRC