With recent (Wayland-enabled) releases of GDM, the greeter (the program that displays and processes the login prompt) is a Wayland application, so the display manager doesn't normally run an X.org instance while it is sitting at the login prompt. Since VirtualGL's GLX back end needs an X.org instance in order to communicate with the GPU, vglserver_config in VGL 2.6.2 and later modifies the display manager configuration so that the greeter uses X.org instead of Wayland (but note that this modification makes it impossible to log in locally to the machine using a Wayland session.) Recent (Wayland-enabled) releases of GDM also use a different instance of X.org for the greeter and the logged-in session. Thus, the expected behavior once you have followed the setup instructions in the VirtualGL User's Guide is:

(a) Whenever the DM is sitting at the login prompt, Display :0 will work as a 3D X server display (VGL_DISPLAY) for all VirtualGL users on the system.

(b) Whenever someone is logged in, Display :1 will work as a 3D X server display (VGL_DISPLAY) for the logged in user only.

Assuming you have properly configured the machine per the instructions in the VirtualGL User's Guide, (b) seems to not be true for your machine. I'm not sure why that's the case. Can you confirm whether (a) is true?

DRC

On 9/13/21 9:07 AM, Jason Edgecombe wrote:
Hello,

I'm having trouble getting VirtualGL to work on Ubuntu 20.04. Running `vglrun
glxinfo`  or any other 3D program just hangs. I have a server with an AMD
Radeon PRO WX 9100 GPU as the 2nd graphics card. I've installed the
amdgpu-pro-21.10-1263777-ubuntu-20.04 AMD driver. I can run glxspheres directly
on the AMD card (DISPLAY=:1), but running `vglrun glxpheres` just hangs.

The log below shows that glxspheres runs fine on the AMD card (DISPLAY=:1)
without vglrun:

```
% env | grep VGL
VGL_FORCEALPHA=1
VGL_COMPRESS=proxy
VGL_DISPLAY=:1
VGL_VERBOSE=1
% DISPLAY=:1 /opt/VirtualGL/bin/glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Visual ID of window: 0x4e7
Context is Direct
OpenGL Renderer: Radeon Pro WX 9100
326.487701 frames/sec - 364.360274 Mpixels/sec
309.610468 frames/sec - 345.525283 Mpixels/sec
327.475757 frames/sec - 365.462944 Mpixels/sec
^C
%
```

Here is an example of `vglrun glxinfo` hanging:

```
% VGL_TRACE=1 vglrun glxinfo
[VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to
[VGL]    10.17.150.240, the IP address of your SSH client.
[VGL] Shared memory segment ID for vglconfig: 10
[VGL 0xc4a0ce40] XOpenDisplay (name=NULL [VGL] VirtualGL v2.6.1 64-bit (Build 20190411)
[VGL] dlopen (filename=libX11-xcb.so.1 flag=258 retval=0x5586355a96b0)
[VGL] dlopen (filename=libxcb.so.1 flag=258 retval=0x7f04c4def530)
[VGL] dlopen (filename=libxshmfence.so.1 flag=258 retval=0x5586355a9d30)
[VGL] dlopen (filename=libxcb-dri3.so.0 flag=258 retval=0x5586355aa310)
[VGL] dlopen (filename=libxcb-dri2.so.0 flag=258 retval=0x5586355aa920)
[VGL] dlopen (filename=libxcb-randr.so.0 flag=258 retval=0x5586355aaf30)
[VGL] dlopen (filename=libxcb-sync.so.1 flag=258 retval=0x5586355ab540)
[VGL] dlopen (filename=libX11.so.6 flag=258[VGL] NOTICE: Replacing dlopen("libX11.so.6") with dlopen("libvglfaker.so")
  retval=0x7f04c59a34f0)
[VGL] dlopen (filename=libxcb-present.so.0 flag=258 retval=0x5586355abc60)
[VGL] dlopen (filename=libxcb-glx.so.0 flag=258 retval=0x5586355ac280)
[VGL] dlopen (filename=libXfixes.so.3 flag=258 retval=0x5586355ac890)
[VGL] dlopen (filename=libXdamage.so.1 flag=258 retval=0x5586355ad080)
[VGL] dlopen (filename=libXext.so.6 flag=258 retval=0x7f04c4dee510)
[VGL] dlopen (filename=libXxf86vm.so.1 flag=258 retval=0x5586355ad750)
[VGL] dlopen (filename=libXau.so.6 flag=258 retval=0x7f04c4a36000)
[VGL] dlopen (filename=libXdmcp.so.6 flag=258 retval=0x7f04c4a36510)
dpy=0x5586355addf0(localhost:10.0) ) 193.939924 ms
name of display: localhost:10.0
[VGL 0xc4a0ce40] glXChooseVisual (dpy=0x5586355addf0(localhost:10.0) screen=0 attrib_list=[0x0004 0x0008=0x0001 0x0009=0x0001 0x000a=0x0001 0x000c=0x0001 0x000d=0x0001 0x000e=0x0001 0x000f=0x0001 0x0010=0x0001 0x0011=0x0001 0x0005 ] glxattribs=[0x000c=0x0001 0x000d=0x0001 0x000e=0x0001 0x000f=0x0001 0x0010=0x0001 0x0011=0x0001 0x0005=0x0001 0x8011=0x0001 0x0008=0x0001 0x0009=0x0001 0x000a=0x0001 0x000b=0x0001 0x8010=0x0006 0x0022=0x8002 ] [VGL] Opening connection to 3D X server :1
[VGL] dlopen (filename=NULL flag=258 retval=0x7f04c59f4190)
```

I had this working fine under Ubuntu 16.04 on the exact same hardware.

Does anyone know how I can fix this?

Thanks,
Jason
---------------------------------------------------------------------------
Jason Edgecombe | Linux Administrator
UNC Charlotte | Office of OneIT
---------------------------------------------------------------------------
If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at
704-687-1943 <tel:704-687-1943>.  Thank you.

--
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/2cd2900c-3018-dc0b-86d9-daee0f5b4c3f%40virtualgl.org.

Reply via email to