<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I'll forward this on to our software guy.  I know he's built a
    previous version using OSMesa, but I think he was trying to avoid it
    this time.  <br>
    <br>
    Thanks for hte information.<br>
    <br>
    <div class="moz-cite-prefix">On 03/31/2016 09:10 PM, Andy Bauer
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>Hi Lloyd,<br>
                  <br>
                </div>
                If you've built ParaView yourself in the past then doing
                it with EGL support shouldn't be any more difficult. The
                link that Utkarsh sent out covers most if not all of the
                necessary information. I'll highlight the fact though
                that you'll need to update your NVIDIA drivers to at
                least 355.11. The dashboard that's testing ParaView with
                EGL is running 358.13.<br>
                <br>
              </div>
              If you're building 5.0 or 5.0.1 it may not have the newest
              stuff for easily finding EGL libraries. For reference, on
              our EGL dashboard machine the location that the default
              NVIDIA driver install puts the EGL libraries and header
              files are:<br>
               EGL_INCLUDE_DIR                  /usr/include<br>
               EGL_LIBRARY                     
              /usr/lib/x86_64-linux-gnu/libEGL.so<br>
               EGL_gldispatch_LIBRARY          
              /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0<br>
               EGL_opengl_LIBRARY              
              /usr/lib/x86_64-linux-gnu/libOpenGL.so<br>
              <br>
            </div>
            Please let us know if you have any problems.<br>
            <br>
          </div>
          Best,<br>
        </div>
        Andy</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Mar 31, 2016 at 4:51 PM,
          Utkarsh Ayachit <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Lloyd,<br>
            <br>
            For a headless server with K80s, you cannot use binaries
            distributed<br>
            from <a moz-do-not-send="true" href="http://paraview.org"
              rel="noreferrer" target="_blank">paraview.org</a>. I'd
            suggesting building ParaView from source with<br>
            EGL support (refer to<br>
            <a moz-do-not-send="true"
href="https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/"
              rel="noreferrer" target="_blank">https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/</a>).<br>
            <br>
            Andy, can you point Lloyd to any addition ParaVIew + EGL
            build<br>
            information that may be useful? Thanks<br>
            <span class="HOEnZb"><font color="#888888"><br>
                Utkarsh<br>
              </font></span>
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
                On Thu, Mar 31, 2016 at 10:36 AM, Lloyd Brown <<a
                  moz-do-not-send="true"
                  href="mailto:lloyd_brown@byu.edu"><a class="moz-txt-link-abbreviated" href="mailto:lloyd_brown@byu.edu">lloyd_brown@byu.edu</a></a>>
                wrote:<br>
                > Well....not exactly.  Just for clarification, this
                is running pvserver,<br>
                > with a completely headless Xorg instance.  I'm then
                connecting my<br>
                > desktop's Paraview frontend instance to it over
                (presumably) a TCP<br>
                > socket.  I'm not actually using SSH x11 forwarding,
                in this case.<br>
                ><br>
                > But to answer your other question, here's the
                similar info from my setup:<br>
                ><br>
                >> bash-4.1$ DISPLAY=:0.0 glxinfo | grep OpenGL<br>
                >> OpenGL vendor string: NVIDIA Corporation<br>
                >> OpenGL renderer string: Tesla K80/PCIe/SSE2<br>
                >> OpenGL version string: 4.5.0 NVIDIA 352.79<br>
                >> OpenGL shading language version string: 4.50
                NVIDIA<br>
                >> OpenGL extensions:<br>
                >> bash-4.1$<br>
                ><br>
                > So, if I'm interpreting that right, I should be
                able up to handle OpenGL<br>
                > v4.5.0.<br>
                ><br>
                > Lloyd<br>
                ><br>
                ><br>
                > On 03/30/2016 08:25 PM, Scott, W Alan wrote:<br>
                >> Lloyd,<br>
                >> I see the same thing,  ... um ... sort of. 
                Mine occurs when ssh -X'ing into a remote blade.  New
                ParaView (i.e., 5.0.0 and later) needs OpenGL 3.2.  I
                suspect that X forwarding isn't supporting OpenGL 3.2.<br>
                >><br>
                >> If I log onto the blade directly, the OGL
                version is sufficient.  But, when ssh -X'ing into it, if
                I do a "glxinfo | grep OpenGL", three of the lines will
                say<br>
                >><br>
                >> OpenGL vendor string: NVIDIA Corporation<br>
                >> OpenGL renderer string: Quadro 3000M/PCIe/SSE2<br>
                >> OpenGL version string: 2.1.2 NVIDIA 337.25<br>
                >><br>
                >> I wonder if you aren't seeing the same thing?<br>
                >><br>
                >><br>
                >> -----Original Message-----<br>
                >> From: ParaView [mailto:<a
                  moz-do-not-send="true"
                  href="mailto:paraview-bounces@paraview.org"><a class="moz-txt-link-abbreviated" href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a></a>]
                On Behalf Of Lloyd Brown<br>
                >> Sent: Wednesday, March 30, 2016 1:37 PM<br>
                >> To: <a moz-do-not-send="true"
                  href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
                >> Subject: [EXTERNAL] [Paraview] BadAlloc Error<br>
                >><br>
                >> Hi, all.<br>
                >><br>
                >> I'm trying to get Paraview 5.0 to interact well
                with the Tesla k80 GPUs in my HPC lab, and I'm
                encountering an interesting error.  I'm hoping that
                someone can point me in the right direction to diagnose
                it.<br>
                >><br>
                >> So, on an HPC node, with some k80s installed,
                I'm launching Xorg (example config attached) as root,
                then launching pvserver<br>
                >> ("DISPLAY=:0.0 pvserver") as my user.  Then
                when I try to connect from the Paraview frontend on my
                desktop, pvserver exits with this error:<br>
                >><br>
                >>> Waiting for client...<br>
                >>> Connection URL: cs://m8g-1-5:11111<br>
                >>> Accepting connection(s): m8g-1-5:11111
                Client connected.<br>
                >>> X Error of failed request:  BadAlloc
                (insufficient resources for<br>
                >>> operation)<br>
                >>>   Major opcode of failed request:  135
                (GLX)<br>
                >>>   Minor opcode of failed request:  34 ()<br>
                >>>   Serial number of failed request:  26<br>
                >>>   Current serial number in output stream: 
                27<br>
                >> Now, according to the guys on the xorg users
                list (<a moz-do-not-send="true"
                  href="https://lists.x.org/archives/xorg/2016-March/057984.html"
                  rel="noreferrer" target="_blank">https://lists.x.org/archives/xorg/2016-March/057984.html</a>),
                this is occurring as a result of the
                glXCreateContextAttribsARB call getting denied resources
                somehow, which lines up with the backtrace from gdb
                (also attached).<br>
                >><br>
                >> Now, under the assumption that pvserver was
                somehow running out of memory, I've verified that the
                problem still occurs when my HPC job requests 64GB
                (which means the cgroup will limit me to that).<br>
                >><br>
                >> Since both the client and server are
                precompiled 5.0 binaries from <a moz-do-not-send="true"
                  href="http://paraview.org" rel="noreferrer"
                  target="_blank">paraview.org</a>, I'm not entirely
                sure where to go here.  Can anyone shed any insight on
                what might be going on?  A misconfiguration in my Xorg
                config?  Some software package I'm missing?<br>
                >><br>
                >> It's worth noting that several GLX-based
                benchmarks (eg. glxgears, glxspheres64, glmark2) and
                utilities (eg. glxinfo, glewinfo) seem to be able to
                interact with the Xorg just fine.<br>
                >><br>
                >> Thanks,<br>
                >><br>
                >> --<br>
                >> Lloyd Brown<br>
                >> Systems Administrator<br>
                >> Fulton Supercomputing Lab<br>
                >> Brigham Young University<br>
                >> <a moz-do-not-send="true"
                  href="http://marylou.byu.edu" rel="noreferrer"
                  target="_blank">http://marylou.byu.edu</a><br>
                >><br>
                ><br>
                > --<br>
                > Lloyd Brown<br>
                > Systems Administrator<br>
                > Fulton Supercomputing Lab<br>
                > Brigham Young University<br>
                > <a moz-do-not-send="true"
                  href="http://marylou.byu.edu" rel="noreferrer"
                  target="_blank">http://marylou.byu.edu</a><br>
                ><br>
                > _______________________________________________<br>
                > Powered by <a moz-do-not-send="true"
                  href="http://www.kitware.com" rel="noreferrer"
                  target="_blank">www.kitware.com</a><br>
                ><br>
                > Visit other Kitware open-source projects at <a
                  moz-do-not-send="true"
                  href="http://www.kitware.com/opensource/opensource.html"
                  rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a></a><br>
                ><br>
                > Please keep messages on-topic and check the
                ParaView Wiki at: <a moz-do-not-send="true"
                  href="http://paraview.org/Wiki/ParaView"
                  rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
                ><br>
                > Search the list archives at: <a
                  moz-do-not-send="true"
                  href="http://markmail.org/search/?q=ParaView"
                  rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a></a><br>
                ><br>
                > Follow this link to subscribe/unsubscribe:<br>
                > <a moz-do-not-send="true"
                  href="http://public.kitware.com/mailman/listinfo/paraview"
                  rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Lloyd Brown
Systems Administrator
Fulton Supercomputing Lab
Brigham Young University
<a class="moz-txt-link-freetext" href="http://marylou.byu.edu">http://marylou.byu.edu</a></pre>
  </body>
</html>