On 11/16/17 4:48 AM, Angel de Vicente wrote:
> In order not to get confused, I will call client to my workstation (in
> this case called "com") and server to the remote machine where the P100
> Nvidia card is (in this case called "deim"), so from my client I do
> vglconnect angelv@deim and in deim is where I want to run vglrun -cl
> com
"In the remote shell session" means on the server machine.
> I wasn't sure if I had to set VGL_PROBEGLX in the client or the server,
> so I tried in both. If set in the client the swrast message doesn't go
> away, but if set in the server it does go away:
On the server machine, in the remote shell session.
> | [angelv@com ~]$ vglconnect angelv@deim
> |
> | [angelv@deim ~]$ setenv VGL_PROBEGLX 0
> | [angelv@deim ~]$ vglrun +v -cl com glxspheres64
> | [VGL] NOTICE: Added /usr/lib64/VirtualGL to LD_LIBRARY_PATH
> | Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
> | [VGL] Shared memory segment ID for vglconfig: 294914
> | [VGL] VirtualGL v2.4 64-bit (Build 20170210)
> | [VGL] Opening connection to 3D X server :0
> | [VGL] NOTICE: Replacing dlopen("/usr/lib64/libdl.so.2") with
> | dlopen("libdlfaker.so")
> | Visual ID of window: 0x21
> | Context is Direct
> | [VGL] Using Pbuffers for rendering
> | OpenGL Renderer: Tesla P100-PCIE-12GB/PCIe/SSE2
> | [VGL] Using 1 / 20 CPU's for compression
> | [VGL] Using pixel buffer objects for readback (BGR --> BGR)
> | [VGL] Client version: 2.1
> | 1097.198122 frames/sec - 1224.473105 Mpixels/sec
> `----
>
>> If my hypothesis is incorrect, then here are other things to try:
>
> So, at this point I don't know if your hypothesis is correct, incorrect
> or both at the same time :-)
It appears that it was correct, although I don't understand why you
aren't seeing GLX_EXT_libglvnd in the glxinfo output. But since setting
VGL_PROBEGLX=0 on the server made the error message go away, clearly
that error message came from libGLX_mesa.so.0, which was being used to
communicate with the 2D (client-side) X display. Perhaps the libglvnd
implementation in Fedora defaults to using Mesa if it can't determine
the appropriate OpenGL vendor for a particular X display.
Long and the short of it: the error is innocuous. Don't worry about
it. You may be able to make it go away permanently by doing `sudo dnf
install mesa-dri-drivers`.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/virtualgl-users/502c029d-3074-ecb8-34ca-18ca47a532af%40virtualgl.org.
For more options, visit https://groups.google.com/d/optout.
