If the vendor can provide more information about how they are querying the driver, then perhaps I can work around the issue in either VirtualGL or TurboVNC. If, for instance, they are using the NV-CONTROL X11 extension, then TurboVNC has support for that, but it has to be explicitly enabled when you start a TurboVNC Server session:
https://cdn.rawgit.com/TurboVNC/turbovnc/2.1.1/doc/index.html#hd009003 Normally this would be done by passing "-nvcontrol :0.0" to /opt/TurboVNC/bin/vncserver. If they are using some nVidia-specific GLX extension, then perhaps VirtualGL simply needs to interpose the function calls related to that extension and advertise the extension when the application queries the available GLX extensions. On 6/2/17 8:02 AM, Peter Tyson wrote: > Thanks for your suggestions. The app is Avizo and the issue is that > on startup it interrogates the driver in some way to determine the > amount of vmem in the system which fails under VNC. When such a zero > value is returned the app then defaults to 4GB present. The vendor > supplied me with an environment variable which can override this > value. > > Peter ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
