OpenGL Error in Fedora 21

[thatbloke]

Hello,

I'm trying to run OpenGL enabled applications inside a Fedora 21 Guest (32-bit) running on a Windows 10 64-bit host.

The 3D acceleration option in the "Display" tab of the Machine settings view is enabled.

When I try to run anything that requires openGL, I am getting the following output in console:

Code: Select all

name of display: :0
libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo

The above is the start of the output from the "glxinfo" command, but omits the rest - if it may be useful to provide further insight into the issue then please let me know.

I have searched for the above errors online, and they generally lead me back to either virtualbox ticket 12941 or virtualbox ticket 13339 (sorry, cannot post urls yet due to new account) which suggests that these problems have been solved with changes to the guest additions - however they are about a year old and I'm seeing this issue with the latest released version of virtualbox and is associated guest additions, Version 5.0.10 r104061. The guest OS is additionally fully updated.

Any feedback or insight anyone is able to provide is appreciated.

[thatbloke]

Nobody got any suggestions?

[loukingjr]

What applications are you trying to run?

If you have 3D acceleration enabled for the guest try disabling it.

[thatbloke]

What applications are you trying to run?

If you have 3D acceleration enabled for the guest try disabling it.

Specifically, Qt Creator or any Qt app. Without 3D acceleration enabled they can run but are EXTREMELY slow. When I try to use the acceleration, so that it can properly use openGL, I get the above error when trying to run any Qt app.

[loukingjr]

With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" to a zip file. Attach the zip here.

What I find somewhat interesting, is on my OSX host, Fedora 22 Mate and Fedora 23 XFCE are considerably faster with 3D disabled.

I take it you are running KDE which I rarely use.

[thatbloke]

With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" to a zip file. Attach the zip here.

What I find somewhat interesting, is on my OSX host, Fedora 22 Mate and Fedora 23 XFCE are considerably faster with 3D disabled.

I take it you are running KDE which I rarely use.

I'm running whatever the default environment for Fedora 21 is, which I believe is actually GNOME.

Please find attached the log you've requested. I ran the VM, logged in, opened a command line, ran "glxinfo" (I still get the above error) and then powered it off.

[loukingjr]

A couple things I noticed in the log. First Windows 10 seems to be taking up a fair amount of memory…

00:00:02.155672 Host RAM: 8107MB total, 2835MB available

Your guest is assigned 2GB of RAM so that might cause a problem.

Your CPU is a 2 core 4 thread CPU. Intel® Core™ i7-5500U
I would try setting the number of CPUs for the guest to one and see how that runs.

BTW, what you are calling errors are just warnings and just mean not all OpenGL extensions are supported. Run glxgears and see what the results are.

[thatbloke]

Hello, thankyou for your continued assistance and suggestions.

I had another VM running at the same time as trying this one, so that's why the RAM available was a little low.

I've dropped it to one CPU core however that's had zero effect.

I found that I could set LIBGL_DEBUG=verbose and then run an app to get more info - when doing this I see some extra debug, out of which the following looks particularly suspect:

Code: Select all

libGL: driver does not expose __driDriverGetExtensions_vboxvideo(): /usr/lib/dri/vboxvideo_dri.so: undefined symbol: __driDriverGetExtensions_vboxvideo

Perhaps this could be related? Is it possible I'm missing something installed on my system which means that the guest additions are not being built correctly? Any idea how I might check for common things that might be missing?

[loukingjr]

Your question exceeds my limited knowledge of Linux. I assume someone with more Linux experience will be along.

[Duanehebert]

I have the same error running a Fedora 21 guest on a Windows 7 host with VB 5.0.10. If I enable 3d acceleration I get a crash at startup or a hung system. If I don't enable 3d acceleration everything seems ok but I get the same libGL errors (libGL error: pci id for fd 4: 80ee:beef, driver (null)) when trying to build an app in QtCreator using Qt5 libs.

If I disable the VirtualBoxAddtions 5.0.10 then enable 3d acceleration and run Qt Creator, I don't have this problem.

Is there any solution or workaround to this yet?

[loukingjr]

If I disable the VirtualBoxAddtions 5.0.10 then enable 3d acceleration and run Qt Creator, I don't have this problem.

I don't know what disable the guest additions means other than to uninstall them. Without guest additions there are no features such as shared folders, shared clipboard, full screen, auto-resize screen or… 3D acceleration.

[Duanehebert]

If I disable the VirtualBoxAddtions 5.0.10 then enable 3d acceleration and run Qt Creator, I don't have this problem.

I don't know what disable the guest additions means other than to uninstall them. Without guest additions there are no features such as shared folders, shared clipboard, full screen, auto-resize screen or… 3D acceleration.

Thanks for the reply.

Right. Uninstall them. And yes this makes virtual box pretty useless. Except I can run my Qt5 based application from QtCreator.

Just to be clear, if I enable 3d acceleration my Fedora 21 guest crashes after I logon. I see there are other posts regarding this with OSX or Windows 8 hosts. I'll post this question somewhere else.

But If I don't enable 3d acceleration I can boot and run QtCreator but launching an application causes the libGL error.

[Duanehebert]

In my case, I am not able to run a linux guest with 3d acceleration for some reason. I get a crash at logon.

But regarding the problems with running QtCreator and Qt5 apps I found a suggestion from a Qt users with similar issues to set LIBGL_ALWAYS_SOFTWARE=1
before launching QtCreator. This works for me.

In my Fedora 21 guest, I added LIBGL_ALWAYS_SOFTWARE=1 in /etc/init.d/functions and restarted. QtCreator loads and the program that I'm building runs.

[loukingjr]

FWIW, Fedora 21 has now reached EOL. Might be time to think about upgrading.

[Duanehebert]

FWIW, Fedora 21 has now reached EOL. Might be time to think about upgrading.

That was fast. 21 was released 1 year ago. But one of my colleagues is still using Fedora 16 so I don't think it's a big rush...