VirtualGL - Revision history

Leo: Added categories and navbox

2021-12-30T01:12:34Z

Added categories and navbox

← Older revision		Revision as of 01:12, 30 December 2021
Line 39:		Line 39:
	*<code>VGL_LOGO</code> will print 'VGL' on the window to show that it's rendering with VirtualGL.		*<code>VGL_LOGO</code> will print 'VGL' on the window to show that it's rendering with VirtualGL.

	~~<br />~~
			{{Navbox Linux}}
			[[Category:Linux]]
			[[Category:LinuxUtilities]]

Leo at 19:36, 11 February 2021

2021-02-11T19:36:48Z

← Older revision		Revision as of 19:36, 11 February 2021
Line 3:		Line 3:
	==Installation==		==Installation==
	Download the RPM packages from VirtualGL's repository (on SourceForge) and install it. You may then use the included helper script at <code>/opt/VirtualGL/bin/vglserver_config</code> to set up your system. The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>.		Download the RPM packages from VirtualGL's repository (on SourceForge) and install it. You may then use the included helper script at <code>/opt/VirtualGL/bin/vglserver_config</code> to set up your system. The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>.

			Applications using VirtualGL are executed using the <code>vglrun</code> script which injects a library that redirects OpenGL calls so they render on a local target display (the <code>VGL_DISPLAY</code>). Because each Xorg server uses a Xauth cookie for authentication, <code>vglrun</code> will also try to read this Xauth cookie from <code>/etc/opt/VirtualGL/vgl_xauth_key</code>. For VirtualGL to work, we also need to write the Xauth cookie at this location for the screen the user is trying to render to.

			The <code>vgl_xauth_key</code> file can be created using the <code>/usr/bin/vglgenkey</code> script or manually using <code>xauth</code>. If using a login manager like LightDM or GDM, you will need to have the login manager run the <code>vglgenkey</code> script on startup. For systems with multiple GPUs, you will need to start a Xorg server on each GPU and have the <code>vgl_xauth_key</code> contain every cookie or somehow setup the user's xauth cookie list prior to running <code>vglrun</code>.

	<br />		<br />

	~~#I had issues with G~~		=== Using the login manager's X11 server ===
	~~#DM working with VirtualGL.~~ Install LightDM and configure the seats to generate a key. {{Highlight
			==== LightDM ====
			Install LightDM and configure the seats to generate a key. {{Highlight
	\| code = [Seat:seat0]		\| code = [Seat:seat0]
	display-setup-script=/usr/bin/vglgenkey		display-setup-script=/usr/bin/vglgenkey
	\| lang = text		\| lang = text
	}}		}}
	~~#After restarting your login manager, verify that <code>/etc/opt/VirtualGL/</code> has a key file.~~

	If you ~~need to tweak~~ <code>xorg.conf</code>~~, you~~ may generate one using Nvidia's <code>nvidia-xconfig</code> utility. ~~You may wish~~ to ~~specify~~ the ~~device~~ the ~~screen is~~ to use ~~by looking up the PCI bus ID and passing it as an argument~~. ~~Eg:~~		=== Starting X11 Manually ===
	{{highlight\|lang=terminal\|code=		This method gives you full control over which Xorg server starts on which GPU.

			Create a <code>xorg.conf</code> file. You may generate one using Nvidia's <code>nvidia-xconfig</code> utility, but this tool doesn't support multiple GPUs. It's a good starting point however, because you just need to duplicate the Screen/Device sections for each of the additional GPUs you want to use with VirtualGL.{{highlight\|lang=terminal\|code=
	# nvidia-xconfig --use-display-device=none --busid="PCI:6:0:0"		# nvidia-xconfig --use-display-device=none --busid="PCI:6:0:0"
	}}		}}

			Create an xauth cookie for each X11 server and then start each X11 server. Merge all cookies into the <code>vgl_xauth_key</code> file so vglrun works.
	==Usage==		==Usage==
	The idea with VirtualGL is that the program you wish to have GPU acceleration renders locally (ie. the remote host that's running the login manager) and VirtualGL then copies the framebuffer back to you. As a result, anything you do run with VirtualGL can appear on the local display which could be a security risk for workstations (such as in a lab setting).		The idea with VirtualGL is that the program you wish to have GPU acceleration renders locally (ie. the remote host that's running the login manager) and VirtualGL then copies the framebuffer back to you. As a result, anything you do run with VirtualGL can appear on the local display which could be a security risk for workstations (such as in a lab setting).

Leo at 19:23, 11 February 2021

2021-02-11T19:23:54Z

← Older revision		Revision as of 19:23, 11 February 2021
Line 2:		Line 2:

	==Installation==		==Installation==
			Download the RPM packages from VirtualGL's repository (on SourceForge) and install it. You may then use the included helper script at <code>/opt/VirtualGL/bin/vglserver_config</code> to set up your system. The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>.
			<br />

	~~#Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it.~~		#I had issues with G
	~~#Run the configuration helper script at <code>/opt/VirtualGL/bin/vglserver_config</code>. You will be asked some questions:~~		#DM working with VirtualGL. Install LightDM and configure the seats to generate a key. {{Highlight
	~~#*If using VNC with TurboVNC or TigerVNC, do not disable XTEST extension~~
	~~#*You may restrict certain users access to the <code>vglusers</code> group when prompted.~~
	~~#*The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>~~
	#I had issues with ~~GDM~~ working with VirtualGL. Install LightDM and configure the seats to generate a key. {{Highlight
	\| code = [Seat:seat0]		\| code = [Seat:seat0]
	display-setup-script=/usr/bin/vglgenkey		display-setup-script=/usr/bin/vglgenkey

Leo: /* Usage */

2021-02-09T18:45:31Z

Usage

← Older revision		Revision as of 18:45, 9 February 2021
Line 1:		Line 1:
	<br />		<br />

	== Installation ==		==Installation==

	# Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it.		#Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it.
	# Run the configuration helper script at <code>/opt/VirtualGL/bin/vglserver_config</code>. You will be asked some questions:		#Run the configuration helper script at <code>/opt/VirtualGL/bin/vglserver_config</code>. You will be asked some questions:
	#* If using VNC with TurboVNC or TigerVNC, do not disable XTEST extension		#*If using VNC with TurboVNC or TigerVNC, do not disable XTEST extension
	#* You may restrict certain users access to the <code>vglusers</code> group when prompted.		#*You may restrict certain users access to the <code>vglusers</code> group when prompted.
	#* The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>		#*The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>
	# I had issues with GDM working with VirtualGL. Install LightDM and configure the seats to generate a key. {{Highlight		#I had issues with GDM working with VirtualGL. Install LightDM and configure the seats to generate a key. {{Highlight
	\| code = [Seat:seat0]		\| code = [Seat:seat0]
	display-setup-script=/usr/bin/vglgenkey		display-setup-script=/usr/bin/vglgenkey
	\| lang = text		\| lang = text
	}}		}}
	# After restarting your login manager, verify that <code>/etc/opt/VirtualGL/</code> has a key file.		#After restarting your login manager, verify that <code>/etc/opt/VirtualGL/</code> has a key file.

	If you need to tweak xorg.conf, you may generate one using Nvidia's nvidia-xconfig utility. You may wish to specify the device the screen is to use by looking up the PCI bus ID and passing it as an argument. Eg:		If you need to tweak <code>xorg.conf</code>, you may generate one using Nvidia's <code>nvidia-xconfig</code> utility. You may wish to specify the device the screen is to use by looking up the PCI bus ID and passing it as an argument. Eg:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# nvidia-xconfig --use-display-device=none --busid="PCI:6:0:0"		# nvidia-xconfig --use-display-device=none --busid="PCI:6:0:0"
Line 21:		Line 21:


	== Usage ==		==Usage==
	The idea with VirtualGL is that the program you wish to have GPU acceleration renders locally (ie. the remote host that's running the login manager) and VirtualGL then copies the framebuffer back to you. As a result, anything you do run with VirtualGL can appear on the local display which could be a security risk for workstations (such as in a lab setting).		The idea with VirtualGL is that the program you wish to have GPU acceleration renders locally (ie. the remote host that's running the login manager) and VirtualGL then copies the framebuffer back to you. As a result, anything you do run with VirtualGL can appear on the local display which could be a security risk for workstations (such as in a lab setting).

	To run a specific application with VirtualGL, use the vglrun command. To help debug issues, use the +v flag to enable verbose logging.		To run a specific application with VirtualGL, use the <code>vglrun</code> command. To help debug issues, use the <code>+v</code> flag to enable verbose logging.

	A few environment variables you should be aware of:		A few environment variables you should be aware of:
	* VGL_DISPLAY should point to the local display with the login manager. (eg. :0)
	* DISPLAY or the -display option should be set to the target display (eg. :1.0, or whatever your display is in a VNC session)		*<code>VGL_DISPLAY</code> should point to the local display with the login manager. (eg. :0)
	* VGL_VERBOSE enables debugging		*<code>DISPLAY</code> or the -display option should be set to the target display (eg. :1.0, or whatever your display is in a VNC session)
	* VGL_LOGO will print 'VGL' on the window to show that it's rendering with VirtualGL		*<code>VGL_VERBOSE</code> enables debugging
			*<code>VGL_LOGO</code> will print 'VGL' on the window to show that it's rendering with VirtualGL.

			<br />

Leo: /* Usage */

2021-02-09T18:39:27Z

Usage

@@ Line 8: / Line 8: @@
 #* You may restrict certain users access to the <code>vglusers</code> group when prompted.
 #* The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>
-# I had issues with GDM working with VirtualGL. Install LightDM and configure the seats to generate a key.
+# I had issues with GDM working with VirtualGL. Install LightDM and configure the seats to generate a key. {{Highlight
 | code = [Seat:seat0]
 display-setup-script=/usr/bin/vglgenkey
@@ Line 15: / Line 14: @@
 }}
 # After restarting your login manager, verify that <code>/etc/opt/VirtualGL/</code> has a key file.

Leo: Created page with "
== Installation == # Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it. # Run the configuration helper script at `/opt/Virt..."`


2021-02-09T18:32:47Z
Created page with "<br />  == Installation ==  # Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it.  # Run the configuration helper script at <code>/opt/Virt..."
New page
<br />



== Installation ==



# Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it. 

# Run the configuration helper script at <code>/opt/VirtualGL/bin/vglserver_config</code>. You will be asked some questions:

#* If using VNC with TurboVNC or TigerVNC, do not disable XTEST extension

#* You may restrict certain users access to the <code>vglusers</code> group when prompted.

#* The script writes to various places., including <code>/etc/security/console.perms</code>, <code>/etc/modprobe.d/virtualgl.conf</code>, <code>/etc/X11/xorg.conf.d/99-virtualgl-dri</code>

# I had issues with GDM working with VirtualGL. Install LightDM and configure the seats to generate a key.

{{Highlight

| code = [Seat:seat0]

display-setup-script=/usr/bin/vglgenkey

| lang = text

}}

# After restarting your login manager, verify that <code>/etc/opt/VirtualGL/</code> has a key file.

VirtualGL - Revision history

Leo: Added categories and navbox

Leo at 19:36, 11 February 2021

Leo at 19:23, 11 February 2021

Leo: /* Usage */

Leo: /* Usage */

Leo: Created page with " == Installation == # Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it. # Run the configuration helper script at /opt/Virt..."

Leo: Created page with "
== Installation == # Download the .rpm packages from VirtualGL's repository (on SourceForge) and install it. # Run the configuration helper script at `/opt/Virt..."`