On 3/27/20 3:32 PM, Hans Peter wrote:
> Can anybody please help me out here?
>
> I installed VirtualGL 2.6.3 on a RHEL8 box, by adding the yum repo
> (https://virtualgl.org/Downloads/YUM)
> && yum install virtualgl
>
> (I don't have physical access to the machine right now, because I'm
> working from home,
> as do everybody else, but I have access with ssh).
>
> Install Nvidia drivers for the Quadro 2000, as according to
> https://access.redhat.com/solutions/4134381 (login needed), looks OK.
>
> Configured VirtualGL according to the UG at
> https://cdn.rawgit.com/VirtualGL/virtualgl/2.6.3/doc/index.html .
>
> Chose "Restrict 3D X server access" and "Restrict framebuffer" to
> vglusers group, added
> myself and root to the group.
It probably is not related to the issue, but be sure to log out and back
in after adding yourself to the vglusers group, so that the new group
permissions can take effect.
> BTW, the configuration threw the error
> rmmod: ERROR: Module nvidia is in use by: nvidia_modeset
> so I did
> rmmod nvidia_drm nvidia_modeset rmmod nvidia; modprobe nvidia
> nvidia_drm nvidia_modeset
> before I restarted gdm (init 5), but I guess this is unrelated to my
> problems, described below.
It isn't necessary to do that. That error message generally just means
that another process (the display manager) is using the driver. That
shouldn't be the case in run level 3, but apparently you aren't the only
one who observed that problem (refer to the earlier post on this same
group.) Perhaps the issue occurs when using the Red Hat distribution of
the nVidia driver, which would explain why I've never seen it (I only
use nVidia's distribution.)
> Logout, and proceeds with section 6.2.1 in the UG: "Sanity Check"
>
> "log back into the server using SSH"
>
> The guide doesn't specify if I should log in as root, or as myself.
> Nor does it
> say if I should use ssh -X or not.
Because it doesn't matter. The UG will specify on a command-by-command
basis if a command needs to be executed as root, so you can use sudo or
su to run those commands. Using 'ssh -X' is never necessary when using
a supported VirtualGL workflow (if you use vglconnect, it runs 'ssh -X'
behind the scenes.) You don't ever need to SSH into the server as root
(and many servers do not support that anyhow.)
> But whatever I try, when I run
> xauth merge /etc/opt/VirtualGL/vgl_xauth_key I get the error "No such
> file". Quite reasonable, as there is no such file. I guess that the
> script /opt/VirtualGL/bin/vglgenkey
> should generate this key, but running it gets me nowhere, as it seems to
> depend on me having a $DISPLAY. The only $DISPLAY I can manage is
> whatever I get with ssh -X, and I'm pretty sure that is not what is
> intended here.
If /etc/opt/VirtualGL/vgl_xauth_key does not exist, that means that
/opt/VirtualGL/bin/vglgenkey was not executed. vglgenkey is executed
within the display manager startup. It isn't meant to be executed manually.
Have you tried rebooting the machine? If that doesn't work, then I can
only suggest editing /opt/VirtualGL/bin/vglgenkey as follows:
--- a/vglgenkey
+++ b/vglgenkey
@@ -12,6 +12,6 @@ fi
if [ -f /etc/opt/VirtualGL/vgl_xauth_key ]; then
rm /etc/opt/VirtualGL/vgl_xauth_key
fi
-$XAUTH -f /etc/opt/VirtualGL/vgl_xauth_key generate $DISPLAY . trusted
timeout 0 ||
- $XAUTH -f /etc/opt/VirtualGL/vgl_xauth_key add $DISPLAY . `$XAUTH
list | awk '{print $3}' | uniq`
+$XAUTH -f /etc/opt/VirtualGL/vgl_xauth_key generate $DISPLAY . trusted
timeout 0 >>/tmp/out 2>&1 ||
+ $XAUTH -f /etc/opt/VirtualGL/vgl_xauth_key add $DISPLAY . `$XAUTH
list | awk '{print $3}' | uniq` >>tmp/out 2>&1
chmod 644 /etc/opt/VirtualGL/vgl_xauth_key
After doing that, restart the display manager and see if /tmp/out
contains any error messages. If /tmp/out doesn't exist, then vglgenkey
is not being executed by the display manager for some reason.
--
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/d331ba60-290d-0014-159a-250240308027%40virtualgl.org.
