On Feb 10, 2023, at 3:37 PM, Jason Edgecombe <jwed...@uncc.edu> wrote:
--
You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGD6%3DuzD%2Bg_7khupBmkht27_CYeT5UeqWsgRYJzmp%2Bj4gg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/6207A2AF-3007-440C-BD21-7E69290ADBF5%40virtualgl.org.
VirtualGL has never enabled SSH tunneling
of the VGL Transport by default, so I'm not sure what "old
behavior" you're referring to. It has always been necessary to
start vglconnect with -s in order to tunnel the VGL Transport
through SSH.
Also, if it is necessary for you to specify '-c proxy', then that's a pretty good indication that you shouldn't be using '-c proxy'. VirtualGL will normally detect whether you are using an X proxy and automatically enable the X11 Transport (which is what '-c proxy' does.) If you aren't actually using an X proxy, then '-c proxy' will result in sending uncompressed images over the network.
What exactly are you trying to accomplish? Do you really want to use VirtualGL with a client-side X display, or do you really want to use VirtualGL with a server-side X display (X proxy) such as TurboVNC or NX?
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGD%3DXTMfAxPQ2giDtyiXMKzULJuK_PLZ4apoLpRsm2FrXw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/81e9cd93-4739-2893-2dd1-dc0aad297b92%40virtualgl.org.
Case 1: VirtualGL will auto-detect the need for the X11 Transport ('-c proxy') based on the value of the DISPLAY environment variable. If DISPLAY starts with ':' or 'unix:', then the X11 Transport will automatically be enabled if no image transport has been explicitly specified. What is the value of the DISPLAY environment variable when using FastX?
Case 2: Yes, but again, '-c proxy' in that
case results in uncompressed images being sent over the
network. You should instead use 'vglconnect -s' to connect to
the VirtualGL server. That will start the VirtualGL Client on
the client machine and set everything up so that the
OpenGL-rendered frames are compressed using libjpeg-turbo and
the JPEG stream is tunneled through SSH. VirtualGL will
automatically use the VGL Transport if it detects that DISPLAY
begins with 'localhost' or the server's hostname. If the SSH_IP
environment variable is set, which it will be in an SSH session,
then VGL_CLIENT will be populated from SSH_IP. If the VirtualGL
Client is running, which it will be if you connect using
vglconnect, then VGL_PORT will be populated from the value of
the _VGLCLIENT_PORT X atom that the VirtualGL Client sets in the
2D X server. JPEG is the default compression scheme with the
VGL Transport, so effectively all you should have to do is
invoke 'vglrun {application}' if you connect using 'vglconnect
-s'.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGCg%3DmfKpAEbuJPD-LYvbcVhPcYYNAkENOZx3s0sWOabOA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/fe55c870-7423-9dbd-e14e-7dea4b2633ee%40virtualgl.org.
GitHub pull requests, but your suggestion has already been implemented in VirtualGL 3.1 beta1. Please test it.
DRC
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGB24WqcMvohW11PPshM5pXx_U60_ZBKMjs8sL-4Kp73sQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/ffba6f3c-30ea-80a5-8359-354d800bd0b0%40virtualgl.org.