3D Acceleration

Postings relating to old VirtualBox pre-releases
Post Reply
gtirloni
Posts: 6
Joined: 5. Sep 2011, 05:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Fedora, CentOS, WinXP

3D Acceleration

Post by gtirloni »

Hardware: Dell Inspiron 15 (i7-5600U) with Radeon R7 M265 GPU
Host: Windows 10 64-bit
Guest: Fedora 24 with Gnome3
VirtualBox: 5.1 BETA3
Guest Additions: 5.1 BETA3

As soon as Chrome 51 is started, the rendering issues start (black boxes, sometimes blinking, etc). This shows up on the terminal:
[4220:4220:0623/041721:ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.CompositorWorker-0x3cf0aae66dc0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
And this appers in VBox.log:
00:02:24.524303 OpenGL Warning: CRserver: NULL context in MakeCurrent 0
00:02:24.558159 OpenGL Warning: cleaning gl error (0x502), ignoring.. (1 out of 5) ..
00:02:24.558488 OpenGL Warning: cleaning gl error (0x502), ignoring.. (2 out of 5) ..
00:02:24.558918 OpenGL Warning: cleaning gl error (0x502), ignoring.. (3 out of 5) ..
00:02:24.559384 OpenGL Warning: cleaning gl error (0x502), ignoring.. (4 out of 5) ..
00:02:24.559671 OpenGL Warning: cleaning gl error (0x502), ignoring.. (5 out of 5) ..
00:02:27.290959 OpenGL Warning: CRServer: context sharing not implemented.
Firefox 47 says the WebGL renderer is "blocked for you gpu because of unresolved driver issues".

GNOME3 seems to behave a bit better under VBox 5.1BETA3, not as bad as in 5.0.22 after starting Chrome.

Disabling 3D acceleration in the machine settings works around this issue.
Post Reply