-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xpra vglrun glxinfo OpenGL not selecting nvidia for renderer #137
Comments
Nothing obvious. Try the "Sanity Check" procedure to verify that you are able to access the GPU through the 3D X server: Also check the environment and make sure someone hasn't done something stupid, such as setting |
Also, it would be helpful if you could reproduce the same error using another X proxy. It's entirely possible that Xpra is attempting to do something novel with VirtualGL and is somehow messing things up. If this issue is specific to Xpra, then it is a matter for the Xpra developers. |
xpra maintainer here, he has already asked us. This is not an xpra bug or a virtualgl bug IMO, just a setup issue. He's using a singularity container and probably does not have access to an accelerated X11 server to begin with.
No. We don't do anything like that. |
@DevinBayly If you can confirm that you are using a container, then that info should have been included in your post, and if you can confirm that VirtualGL works without the container, then this is not our problem. |
Hi Antoine! I'll have to work with the infrastructure team so that we can get access to the X11 server. Yes, I'm using a singularity container. But we haven't been able to make a I'll check out the Sanity check that you recommend. I think its going to be a bit more complex since the display variable only exists when I run the actual xpra commands, but I believe I'll be able to pass these commands as a script to execute
or this
|
Then you should really fix this problem before making it more complicated. |
good point, I'll try to focus on that before trying to bring xpra or singularity into the mix. I'll close this, and if other issues come up I'll submit them separately. |
hello there. |
@crazyleeth Please do not hijack other issues, particularly issues that are closed and which may or may not be related to yours. Post a new issue. |
Hello there,
I'm setting up a means to give users of an HPC access to Graphical Applications using nvidia hardware included in allocated sessions, however all the configuration I've performed hasn't changed the default renderer that OpenGL is trying to use
OpenGL Renderer: llvmpipe (LLVM 9.0, 256 bits)
.I've performed the following steps, please let me know if I'm missing anything
following the instructions here https://virtualgl.org/Documentation/HeadlessNV we ran
nvidia-xconfig --query-gpu-info
which showed an nvidia gpu at PCI:32:0:0then we ran
nvidia-xconfig -a --allow-empty-initial-configuration --virtual=1920x1200 --busid PCI:32:0:0
and that made a new /etc/X11/xorg.conf with the following contents
Then I tried a couple of things with xpra, but in both cases the vglrun command didn't change the renderer to the nvidia hardware.
I launched an xterm window from this same interactive session, and tried to run
vglrun glxspheres64
but it still showed the line that the OpenGL renderer was using llvm pipeand the fps was around 20, and no programs were active in the
nvidia-smi
report. I'm convinced this isn't an issue with xpra, but with the way I configured the VirtualGL, anything obvious I'm missing?The text was updated successfully, but these errors were encountered: