All good. Can confirm 2.6.2 fixes this issue. On Tuesday, April 16, 2019 at 1:00:04 PM UTC+10, DRC wrote: > > Try the latest 2.6.x pre-release build. This has likely been fixed > already. > > https://virtualgl.org/DeveloperInfo/PreReleases > > On 4/15/19 7:16 PM, Jafaruddin Lie wrote: > > Hi all > > Firstly, I would like to say that vglrun has been working very well > > for us either from within the container or on the host. So I just > > Recently, we deployed a new partition on our RHEL cluster running > > Nvidia P4 + latest 418.40.04 driver. > > > > Vglrun running from the host is working fine, but sort-of works from > > the container. > > > > What works from the container: > > glxsphere64 > > glxinfo -c (log attached glxinfo-c.txt) > > > > What doesn't work from the container: > > glxinfo (logs attached glxinfo.txt) > > Some apps (and glxinfo) crash with this error: > > > > [VGL] ERROR: in glXGetConfig-- > > [VGL] 1115: Could not obtain RGB visual on the server suitable for > > off-screen rendering > > > > The same tests work on our other partitions running other Nvidia cards > > and 391.x drivers. > > I understand that this might be a Singularity issue, but I would like > > to get as much detail as possible from VirtualGL before I go on > > Singularity forum. DRC, can you help me troubleshoot this? > > > > Thanks!! > > > > > > >
-- 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/e67a215c-5826-4e5e-830f-20667dfd4271%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
