VirtualGL and TurboVNC: extension “GLX” missing on display “:0.0”











up vote
4
down vote

favorite












I have a remote computer on AWS (EC2 gl2.2xlarge) with Nvidia GRID card K520 and want to remotely render 3D graphics. I use Ubuntu 14.04 - 64 bit running Unity desktop. Remote and local. For remote connection and OpenGL rendering we use VirtualGL and TurboVNC (*amd64.deb).



I properly installed VirtualGL and TurboVNC and Nvidia 352.63 drivers ( cuda 7.0, because according to this post cuda 7.5 is unstable - which was also unstable for me ).



As I understand VirtualGL uses display :0 and TurboVNC uses display :1 on remote machine.



When I connect to the remote machine and I want to run a 3D app (via vglrun ) it gives me error:



extension "GLX" missing on display ":0.0".



I don't undrestand how VirtualGL works on a remote machine with TurboVNC, how it uses the display :0 and if it's ok.



Do I need something to setup (.conf, graphic driver). I tried installing it over and over, tried serching for answer, but I didn't find a solution.



I can establish connection via TurboVNC with no problem, but vglrun gives me the mentioned erros. Can the problem be in set x.org settings ?



Thanks










share|improve this question


























    up vote
    4
    down vote

    favorite












    I have a remote computer on AWS (EC2 gl2.2xlarge) with Nvidia GRID card K520 and want to remotely render 3D graphics. I use Ubuntu 14.04 - 64 bit running Unity desktop. Remote and local. For remote connection and OpenGL rendering we use VirtualGL and TurboVNC (*amd64.deb).



    I properly installed VirtualGL and TurboVNC and Nvidia 352.63 drivers ( cuda 7.0, because according to this post cuda 7.5 is unstable - which was also unstable for me ).



    As I understand VirtualGL uses display :0 and TurboVNC uses display :1 on remote machine.



    When I connect to the remote machine and I want to run a 3D app (via vglrun ) it gives me error:



    extension "GLX" missing on display ":0.0".



    I don't undrestand how VirtualGL works on a remote machine with TurboVNC, how it uses the display :0 and if it's ok.



    Do I need something to setup (.conf, graphic driver). I tried installing it over and over, tried serching for answer, but I didn't find a solution.



    I can establish connection via TurboVNC with no problem, but vglrun gives me the mentioned erros. Can the problem be in set x.org settings ?



    Thanks










    share|improve this question
























      up vote
      4
      down vote

      favorite









      up vote
      4
      down vote

      favorite











      I have a remote computer on AWS (EC2 gl2.2xlarge) with Nvidia GRID card K520 and want to remotely render 3D graphics. I use Ubuntu 14.04 - 64 bit running Unity desktop. Remote and local. For remote connection and OpenGL rendering we use VirtualGL and TurboVNC (*amd64.deb).



      I properly installed VirtualGL and TurboVNC and Nvidia 352.63 drivers ( cuda 7.0, because according to this post cuda 7.5 is unstable - which was also unstable for me ).



      As I understand VirtualGL uses display :0 and TurboVNC uses display :1 on remote machine.



      When I connect to the remote machine and I want to run a 3D app (via vglrun ) it gives me error:



      extension "GLX" missing on display ":0.0".



      I don't undrestand how VirtualGL works on a remote machine with TurboVNC, how it uses the display :0 and if it's ok.



      Do I need something to setup (.conf, graphic driver). I tried installing it over and over, tried serching for answer, but I didn't find a solution.



      I can establish connection via TurboVNC with no problem, but vglrun gives me the mentioned erros. Can the problem be in set x.org settings ?



      Thanks










      share|improve this question













      I have a remote computer on AWS (EC2 gl2.2xlarge) with Nvidia GRID card K520 and want to remotely render 3D graphics. I use Ubuntu 14.04 - 64 bit running Unity desktop. Remote and local. For remote connection and OpenGL rendering we use VirtualGL and TurboVNC (*amd64.deb).



      I properly installed VirtualGL and TurboVNC and Nvidia 352.63 drivers ( cuda 7.0, because according to this post cuda 7.5 is unstable - which was also unstable for me ).



      As I understand VirtualGL uses display :0 and TurboVNC uses display :1 on remote machine.



      When I connect to the remote machine and I want to run a 3D app (via vglrun ) it gives me error:



      extension "GLX" missing on display ":0.0".



      I don't undrestand how VirtualGL works on a remote machine with TurboVNC, how it uses the display :0 and if it's ok.



      Do I need something to setup (.conf, graphic driver). I tried installing it over and over, tried serching for answer, but I didn't find a solution.



      I can establish connection via TurboVNC with no problem, but vglrun gives me the mentioned erros. Can the problem be in set x.org settings ?



      Thanks







      nvidia xorg virtualgl






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 20 '16 at 9:33









      Michal Gallovic

      12114




      12114






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          The problem was, that there was only 1 X server running, so I only had to do
          sudo xinit &



          after that, vglrun started to work!



          EDIT:



          if anyone stumbles upon the same problem, this stackoverflow answer helped me a lot:
          https://stackoverflow.com/questions/34805794/virtualgl-and-turbovnc-extension-glx-missing-on-display-0-0






          share|improve this answer























          • the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
            – harveyslash
            Nov 20 '16 at 16:21










          • It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
            – zaxliu
            Sep 25 '17 at 8:38













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f723275%2fvirtualgl-and-turbovnc-extension-glx-missing-on-display-0-0%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          The problem was, that there was only 1 X server running, so I only had to do
          sudo xinit &



          after that, vglrun started to work!



          EDIT:



          if anyone stumbles upon the same problem, this stackoverflow answer helped me a lot:
          https://stackoverflow.com/questions/34805794/virtualgl-and-turbovnc-extension-glx-missing-on-display-0-0






          share|improve this answer























          • the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
            – harveyslash
            Nov 20 '16 at 16:21










          • It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
            – zaxliu
            Sep 25 '17 at 8:38

















          up vote
          0
          down vote













          The problem was, that there was only 1 X server running, so I only had to do
          sudo xinit &



          after that, vglrun started to work!



          EDIT:



          if anyone stumbles upon the same problem, this stackoverflow answer helped me a lot:
          https://stackoverflow.com/questions/34805794/virtualgl-and-turbovnc-extension-glx-missing-on-display-0-0






          share|improve this answer























          • the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
            – harveyslash
            Nov 20 '16 at 16:21










          • It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
            – zaxliu
            Sep 25 '17 at 8:38















          up vote
          0
          down vote










          up vote
          0
          down vote









          The problem was, that there was only 1 X server running, so I only had to do
          sudo xinit &



          after that, vglrun started to work!



          EDIT:



          if anyone stumbles upon the same problem, this stackoverflow answer helped me a lot:
          https://stackoverflow.com/questions/34805794/virtualgl-and-turbovnc-extension-glx-missing-on-display-0-0






          share|improve this answer














          The problem was, that there was only 1 X server running, so I only had to do
          sudo xinit &



          after that, vglrun started to work!



          EDIT:



          if anyone stumbles upon the same problem, this stackoverflow answer helped me a lot:
          https://stackoverflow.com/questions/34805794/virtualgl-and-turbovnc-extension-glx-missing-on-display-0-0







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited May 23 '17 at 12:39









          Community

          1




          1










          answered Jan 20 '16 at 11:34









          Michal Gallovic

          12114




          12114












          • the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
            – harveyslash
            Nov 20 '16 at 16:21










          • It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
            – zaxliu
            Sep 25 '17 at 8:38




















          • the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
            – harveyslash
            Nov 20 '16 at 16:21










          • It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
            – zaxliu
            Sep 25 '17 at 8:38


















          the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
          – harveyslash
          Nov 20 '16 at 16:21




          the problem with this is, the actual display that my server is physically connected to , gets black. Any way to keep both things ?
          – harveyslash
          Nov 20 '16 at 16:21












          It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
          – zaxliu
          Sep 25 '17 at 8:38






          It seems you already have an X server running on your server (otherwise you won't have anything that can turn black in the first place). It is likely that your physical display turns black since you want to start a second X server on the save GPU. Actually, you don't need a second one. Just find which DISPLAY the first X server uses and point vglrun to that display with the -display option.
          – zaxliu
          Sep 25 '17 at 8:38




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f723275%2fvirtualgl-and-turbovnc-extension-glx-missing-on-display-0-0%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Quarter-circle Tiles

          build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

          Mont Emei