Thanks I installed 2.5.3 (pre-release stable) and get glxinfo outpu.  I 
have absolutely no idea what I'm doing so I don't know if the below data 
points between the ESXi web console and the TurboVNC sessions are even 
meaningful at all, but here they are.

ESXi web console FULL SCREEN (128MB video ram, 1GB 3D video ram) TurboVNC 
FULL SCREEN (128MB video ram, 1GB 3D video ram)
[fedx@new-host-21 ~]$ glxinfo | grep -i opengl [fedx@new-host-21 ~]$ glxinfo
OpenGL vendor string: VMware, Inc. name of display: :1.0
OpenGL renderer string: SVGA3D; build: RELEASE; LLVM; Error: couldn't find 
RGB GLX visual or fbconfig
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.2.4 
[fedx@new-host-21 
~]$ /opt/VirtualGL/bin/glxinfo
OpenGL core profile shading language version string: 3.30 name of display: 
:1.0
OpenGL core profile context flags: (none) Error: couldn't find RGB GLX 
visual or fbconfig
OpenGL core profile profile mask: core profile Error: couldn't find RGB GLX 
visual or fbconfig
OpenGL core profile extensions: 
OpenGL version string: 3.0 Mesa 17.2.4 
OpenGL shading language version string: 1.30 
OpenGL context flags: (none) 
OpenGL extensions: 
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.2.4 
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 
OpenGL ES profile extensions: 
[fedx@new-host-21 ~]$ glxinfo | grep -i direct 
direct rendering: Yes 
GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_direct_state_access, 
[fedx@new-host-21 ~]$ vglrun glxinfo | grep -i opengl [fedx@new-host-21 ~]$ 
vglrun glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc. OpenGL vendor string: VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE; LLVM; OpenGL renderer 
string: SVGA3D; build: RELEASE; LLVM;
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.2.4 OpenGL 
core profile version string: 3.3 (Core Profile) Mesa 17.2.4
OpenGL core profile shading language version string: 3.30 OpenGL core 
profile shading language version string: 3.30
OpenGL core profile context flags: (none) OpenGL core profile context 
flags: (none)
OpenGL core profile profile mask: core profile OpenGL core profile profile 
mask: core profile
OpenGL core profile extensions: OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.2.4 OpenGL version string: 3.0 Mesa 
17.2.4
OpenGL shading language version string: 1.30 OpenGL shading language 
version string: 1.30
OpenGL context flags: (none) OpenGL context flags: (none)
OpenGL extensions: OpenGL extensions:
[fedx@new-host-21 ~]$ vglrun glxinfo | grep -i direct [fedx@new-host-21 ~]$ 
vglrun glxinfo | grep -i direct
direct rendering: Yes direct rendering: Yes
GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_direct_state_access, 
GL_ARB_depth_buffer_float, 
GL_ARB_depth_clamp, GL_ARB_direct_state_access,
[fedx@new-host-21 ~]$ /opt/VirtualGL/bin/glxinfo | grep -i opengl 
[fedx@new-host-21 
~]$ vglrun /opt/VirtualGL/bin/glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc. OpenGL vendor string: VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE; LLVM; OpenGL renderer 
string: SVGA3D; build: RELEASE; LLVM;
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.2.4 OpenGL 
core profile version string: 3.3 (Core Profile) Mesa 17.2.4
OpenGL core profile shading language version string: 3.30 OpenGL core 
profile shading language version string: 3.30
OpenGL core profile extensions: OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.2.4 OpenGL version string: 3.0 Mesa 
17.2.4
OpenGL shading language version string: 1.30 OpenGL shading language 
version string: 1.30
OpenGL extensions: OpenGL extensions:
[fedx@new-host-21 ~]$ /opt/VirtualGL/bin/glxinfo | grep -i direct 
[fedx@new-host-21 
~]$ vglrun /opt/VirtualGL/bin/glxinfo | grep -i direct
direct rendering: Yes direct rendering: Yes
GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_direct_state_access, 
GL_ARB_depth_buffer_float, 
GL_ARB_depth_clamp, GL_ARB_direct_state_access,
[fedx@new-host-21 ~]$ glxgears [fedx@new-host-21 ~]$ glxgears
5146 frames in 5.0 seconds = 1029.182 FPS Error: couldn't get an RGB, 
Double-buffered visual
5265 frames in 5.0 seconds = 1052.870 FPS 
5368 frames in 5.0 seconds = 1073.427 FPS 
5412 frames in 5.0 seconds = 1082.240 FPS 
5563 frames in 5.0 seconds = 1112.448 FPS 
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" 
after 110126 requests (110126 known processed) with 0 events remaining. 
[fedx@new-host-21 ~]$ vglrun glxgears [fedx@new-host-21 ~]$ vglrun glxgears
2580 frames in 5.0 seconds = 515.841 FPS 201 frames in 5.0 seconds = 40.037 
FPS
2784 frames in 5.0 seconds = 556.626 FPS 211 frames in 5.0 seconds = 42.108 
FPS
2766 frames in 5.0 seconds = 553.048 FPS 221 frames in 5.0 seconds = 44.197 
FPS
2610 frames in 5.0 seconds = 521.943 FPS 232 frames in 5.0 seconds = 46.360 
FPS
2630 frames in 5.0 seconds = 525.953 FPS 190 frames in 5.0 seconds = 37.952 
FPS
2883 frames in 5.0 seconds = 576.446 FPS 201 frames in 5.0 seconds = 40.046 
FPS
[VGL] ERROR: in readback-- 212 frames in 5.0 seconds = 42.252 FPS
[VGL] 262: Window has been deleted by window manager 204 frames in 5.0 
seconds = 40.604 FPS
[VGL] ERROR: in readback--
[VGL] 262: Window has been deleted by window manager
[fedx@new-host-21 ~]$ /opt/VirtualGL/bin/glxspheres64 [fedx@new-host-21 ~]$ 
/opt/VirtualGL/bin/glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres) Polygons in 
scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x18b ERROR in line 620:
Context is Direct Could not obtain RGB visual with requested properties
OpenGL Renderer: SVGA3D; build: RELEASE; LLVM; 
14.427034 frames/sec - 12.307991 Mpixels/sec 
14.599781 frames/sec - 12.455365 Mpixels/sec 
14.555702 frames/sec - 12.417760 Mpixels/sec 
14.766685 frames/sec - 12.597754 Mpixels/sec 
14.757438 frames/sec - 12.589866 Mpixels/sec 
14.907388 frames/sec - 12.717791 Mpixels/sec 
14.677705 frames/sec - 12.521844 Mpixels/sec 
14.635537 frames/sec - 12.485870 Mpixels/sec 
13.851766 frames/sec - 11.817219 Mpixels/sec 
13.691890 frames/sec - 11.680825 Mpixels/sec 
14.490204 frames/sec - 12.361883 Mpixels/sec 
[fedx@new-host-21 ~]$ vglrun /opt/VirtualGL/bin/glxspheres64 [fedx@new-host-21 
~]$ vglrun /opt/VirtualGL/bin/glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres) Polygons in 
scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x21 Visual ID of window: 0x21
Context is Direct Context is Direct
OpenGL Renderer: SVGA3D; build: RELEASE; LLVM; OpenGL Renderer: SVGA3D; 
build: RELEASE; LLVM;
10.673893 frames/sec - 11.912065 Mpixels/sec 11.245267 frames/sec - 
12.549717 Mpixels/sec
10.693061 frames/sec - 11.933456 Mpixels/sec 12.225536 frames/sec - 
13.643698 Mpixels/sec
10.570159 frames/sec - 11.796298 Mpixels/sec 12.358527 frames/sec - 
13.792116 Mpixels/sec
11.909893 frames/sec - 13.291440 Mpixels/sec 11.929632 frames/sec - 
13.313469 Mpixels/sec
11.643979 frames/sec - 12.994681 Mpixels/sec 12.103724 frames/sec - 
13.507756 Mpixels/sec
11.574011 frames/sec - 12.916597 Mpixels/sec 12.423287 frames/sec - 
13.864388 Mpixels/sec
11.181071 frames/sec - 12.478075 Mpixels/sec 11.867817 frames/sec - 
13.244483 Mpixels/sec
11.827372 frames/sec - 13.199347 Mpixels/sec 11.939841 frames/sec - 
13.324863 Mpixels/sec
11.812309 frames/sec - 13.182537 Mpixels/sec 12.089727 frames/sec - 
13.492135 Mpixels/sec
11.804325 frames/sec - 13.173627 Mpixels/sec 11.987084 frames/sec - 
13.377585 Mpixels/sec
11.901313 frames/sec - 13.281866 Mpixels/sec 12.250638 frames/sec - 
13.671712 Mpixels/sec
11.663146 frames/sec - 13.016071 Mpixels/sec 12.321177 frames/sec - 
13.750433 Mpixels/sec
11.327337 frames/sec - 12.641308 Mpixels/sec 11.714833 frames/sec - 
13.073753 Mpixels/sec
11.717028 frames/sec - 13.076203 Mpixels/sec 11.479754 frames/sec - 
12.811405 Mpixels/sec
10.537009 frames/sec - 11.759302 Mpixels/sec [fedx@new-host-21 ~]$
[fedx@new-host-21 ~]$ 
On Monday, January 8, 2018 at 1:37:34 PM UTC-5, DRC wrote:
>
> That's a known bug in our distribution of glxinfo (it wasn't properly 
> handling indirect OpenGL environments.)  Should be fixed in the latest 
> 2.5.x pre-release build: 
> https://virtualgl.org/DeveloperInfo/PreReleases 
>
> One wonders why the context is indirect, however.  Hmmm...  When you log 
> into the "local" display in the VM guest and run glxinfo, is the context 
> still indirect?  If so, then apparently it's a limitation of the ESXi 
> system.  If not (i.e. if the context is indirect only when attempting to 
> access the 3D X server from the login screen), then vglserver_config 
> might be misconfiguring something. 
>
> DRC 
>
> On 1/8/18 12:10 PM, KAJINOFE wrote: 
> > Thanks for the response.  Once the VM Fedora is installed with the 3D 
> > enabled, I am able to get a proper output for glxinfo: 
> > 
> *********************************************************************************************
>  
>
> > [fedgf@new-host-18 ~]$ glxinfo | grep -i Opengl 
> > OpenGL vendor string: VMware, Inc. 
> > OpenGL renderer string: SVGA3D; build: RELEASE;  LLVM; 
> > OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.2.4 
> > OpenGL core profile shading language version string: 3.30 
> > OpenGL core profile context flags: (none) 
> > OpenGL core profile profile mask: core profile 
> > OpenGL core profile extensions: 
> > OpenGL version string: 3.0 Mesa 17.2.4 
> > OpenGL shading language version string: 1.30 
> > OpenGL context flags: (none) 
> > OpenGL extensions: 
> > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.2.4 
> > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 
> 3.00 
> > OpenGL ES profile extensions: 
> > [fedgf@new-host-18 ~]$ 
> > 
> *********************************************************************************************
>  
>
> > 
> > but after I install VirtualGL by following the doc 
> > <https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/index.html>(answered 
>
> > No to all 3 questions), I'm getting the following error: 
> > 
> *********************************************************************************************
>  
>
> > xdpyinfo -display :0 <-- output fine 
> > 
> *********************************************************************************************
>  
>
> > /opt/VirtualGL/bin/glxinfo -display :0 -c <-- I get the below error 
> > Xlib: sequence lost (0x10019 > 0x19) in reply type 0x0! 
> > X Error of failed request:  GLXBadContext 
> > Major opcode of failed request:  154 (GLX) 
> > Minor opcode of failed request:  6 (X_GLXIsDirect) 
> > Serial number of failed request:  25 
> > Current serial number in output stream:  25 
> > 
> *********************************************************************************************
>  
>
> > 
> > My goal for all of this was to get some kind of 3D acceleration for the 
> > VM without a GPU which I think is better than nothing.  If there's an 
> > obvious error in my setup, please let me know, thank you. 
> > 
> > On Monday, January 8, 2018 at 12:31:09 PM UTC-5, DRC wrote: 
> > 
> >     I'm not 100% clear on how ESXi works, but in general, if the X 
> server 
> >     running in the VM guest is able to render OpenGL with hardware 
> >     acceleration, then it should be possible to use VirtualGL in the VM 
> >     guest.  That's the strategy for VirtualGL integration, in general. 
>  Get 
> >     3D acceleration working without VirtualGL first, then add VirtualGL. 
> > 
> >     If there is no physical GPU in the server machine, however, then 
> there 
> >     is no point to using VirtualGL, since VirtualGL is fundamentally a 
> >     mechanism for virtualizing physical GPU resources so that those 
> >     resources can be used remotely and shared by multiple users and 
> >     applications. 
> > 
> >     On 1/8/18 10:35 AM, KAJINOFE wrote: 
> >     > Hello, 
> >     > Is it possible to use VirtualGL with the following setup? 
> >     > 
> >     > ESXi 6.5 
> >     > GPU: none (no discrete GPU, no integrated GPU) 
> >     > VM:  Linux (Fedora (GNOME X11) with SVGA II 3D enabled) 
> >     > 
> >     > I'm trying to remote into the above VM with TurboVNC+VirtualGL 
> installed 
> >     > on the VM and using TurboVNC on my laptop (Ubuntu) and get 3D 
> >     > acceleration and was wondering if this is even possible without a 
> real 
> >     > GPU but with VMware's 3D offerings on ESXi. 
> >     > 
> >     > Thank you. 
> > 
> > -- 
> > 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] <javascript:> 
> > <mailto:[email protected] <javascript:>>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/virtualgl-users/8da9910d-3eb3-4458-979a-047a8faee22c%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/virtualgl-users/8da9910d-3eb3-4458-979a-047a8faee22c%40googlegroups.com?utm_medium=email&utm_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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/3279e553-35ba-4ada-8ac3-2825deee4115%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to