Thank you very much. It worked! My application can show beautiful 3D
rendering in VNC with vglrun.
I just use another vncviewer (realvnc). I will try TurboVNC later, but even
now the performance is pretty good.
Thank you again for the help. This is great tool.
On Wed, Feb 15, 2017 at 12:43 PM, DRC <dcomman...@users.sourceforge.net>
wrote:
> That is all normal. The rmmod error is telling you that the nVidia
> module is in use, which is why the subsequent message tells you to run
> 'rmmod nvidia' with the DM stopped in order to remove the module. That
> is only necessary if you want to activate VGL without rebooting. Since
> you rebooted, you're good.
>
> The TurboVNC display will not have a GLX extension. That's why
> VirtualGL exists. VirtualGL will redirect GLX calls from an OpenGL
> application to display :0, which has a hardware-accelerated GLX extension.
>
> Connect to the TurboVNC session and run
>
> vglrun {your_application}
>
> and it should work.
>
>
> On 2/15/17 11:38 AM, Wei Liu wrote:
> > Darrel,
> >
> > Thanks for the information. I followed your suggestion and created a
> > xorg.conf file. Then I stopped the display manager, and run
> > 'vglserver_config'. After answering questions, I got the following error:
> >
> > ====== vglserver_config output =======
> >
> > .. Creating /etc/modprobe.d/virtualgl.conf to set requested permissions
> > for____
> >
> > /dev/nvidia* ...____
> >
> > ... Attempting to remove nvidia module from memory so device
> permissions____
> >
> > will be reloaded ...____
> >
> > *rmmod: ERROR: Module nvidia is in use by: nvidia_modeset nvidia_uvm____*
> >
> > ... Granting write permission to /dev/nvidia-uvm /dev/nvidia-uvm-tools
> > /dev/nvid ia0 /dev/nvidia1 /dev/nvidia2 /dev/nvidia3 /dev/nvidia4
> > /dev/nvidia5 /dev/nvidia 6 /dev/nvidia7 /dev/nvidiactl for all
> > users ...____
> >
> > ... Granting write permission to /dev/dri/card0 for all users ...____
> >
> > ... /etc/X11/xorg.conf has been saved as /etc/X11/xorg.conf.orig.vgl
> ...____
> >
> > ... Modifying /etc/X11/xorg.conf to enable DRI permissions____
> >
> > for all users ...____
> >
> > ... /etc/lightdm/lightdm.conf has been saved as
> > /etc/lightdm/lightdm.conf.orig.v gl ...____
> >
> > ... Adding display-setup-script=xhost +LOCAL: to
> > /etc/lightdm/lightdm.conf ...____
> >
> > __ __
> >
> > Done. You must restart the display manager for the changes to take
> > effect.____
> >
> > __ __
> >
> > IMPORTANT NOTE: Your system uses modprobe.d to set device permissions.
> > You____
> >
> > must execute rmmod nvidia with the display manager stopped in order for
> > the____
> >
> > new device permission settings to become effective.
> >
> > ===== end of vglserver_config =======
> >
> >
> > I chose 'no' to all the questions, since I don't worry about security in
> > our environment.
> >
> >
> > Then I installed TubroVNC and run vncserver to get a new vnc session at
> > port 3.
> >
> >
> > If I run DISPLAY=:0 glxinfo, I can see direct rendering is yes, and glx
> > vendor string is Nvidia, but if I run DISPLAY=:3 glxinfo, I got error
> > "could not find RGB GLX visual or fbconfig".
> >
> >
> > xdpyinfo -display :3 shows vendor string is TubroVNC...
> >
> >
> > I also reboot the system, but got the same results. I attached the
> > output log of runnining xdpyinfo and glxinfo on port 0 and 3
> > respectively. (the file name has 0 and 3 for the port number).
> >
> >
> > Did I miss anything? Where should I start troubleshooting?
> >
> >
> > Thanks for the help!
> >
> >
> >
> >
> >
> > On Tue, Feb 14, 2017 at 11:53 PM, DRC <dcomman...@users.sourceforge.net
> > <mailto:dcomman...@users.sourceforge.net>> wrote:
> >
> > You can use headless GPUs with VirtualGL. Install the nVidia
> > proprietary drivers (I believe Ubuntu provides a package for these),
> > then run:
> >
> > nvidia-xconfig -a --use-display-device=None --virtual=1920x1200
> >
> > (I don't think the resolution specified for --virtual matters, since
> > it's headless.)
> >
> > Run vglserver_config to grant access to the X server while the
> display
> > manager is sitting at the login prompt, then restart the display
> > manager, and ideally you should be able to do
> >
> > xauth merge /etc/opt/VirtualGL/vgl_xauth_key
> > DISPLAY=:0 glxinfo
> >
> > and glxinfo should report that it is using the nVidia OpenGL
> renderer.
> >
> > On 2/14/17 10:03 PM, Wei Liu wrote:
> > > Hi VirtualGL users,
> > >
> > > I need your help on a set up of virtualGL, or decide if I can use
> > > virtualGL to solve my problem.
> > >
> > > My setup: a Ubunt 14.04 server called 'roundvalley' has multiple
> Nvidia
> > > GPUs for parallel computing, but they do not have any
> > > VGA/DVI/DisplayPort and not connected to monitor. The only
> onboard-card
> > > connected to a monitor does not have 3D capability, and Ubuntu
> > > automatically load a kernel driver module (I forgot the module
> name) for
> > > this onboard card.
> > >
> > > Client side is Windows. My goal is to use VNC to connect to the
> server
> > > and run 3D application (need OpenGL) in my VNC session.
> > >
> > > My question is, can I configure virtualGL to use any of Nvidia GPU
> even
> > > they are not used for display currently?
> > >
> > > I read the official document and found:
> > > ==== user doc =====
> > > 6.2 Using VirtualGL with Multiple GPUs
> > >
> > > VirtualGL can redirect the OpenGL commands from a 3D application
> to any
> > > GPU in the server machine. In order for this to work, however, all
> of
> > > the GPUs must be attached to different screens on the same X
> server or
> > > to different X servers.
> > > ====== end user doc ======
> > >
> > > Does it mean the GPU need to connect to physical screens, or some
> > > definitions in X.org file?
> > >
> > > I appreciate your help.
> > >
> > > Thanks,
> > > Wei
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> > _______________________________________________
> > VirtualGL-Users mailing list
> > VirtualGL-Users@lists.sourceforge.net
> > <mailto:VirtualGL-Users@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/virtualgl-users
> > <https://lists.sourceforge.net/lists/listinfo/virtualgl-users>
> >
> >
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> >
> >
> >
> > _______________________________________________
> > VirtualGL-Users mailing list
> > VirtualGL-Users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/virtualgl-users
> >
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> VirtualGL-Users mailing list
> VirtualGL-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
