[5.2.0] OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
Posted: 22. Nov 2017, 07:12
Hi,
First, I tried Firefox after the upgrade of VBox 5.2 and I could not open up Firefox window at all. Rolling back to previous versions of Firefox would not work either.
Reinstalling Gnome desktop and everything did not help. I almost had to reinstalled the whole system to get things work.
Fortunately, I discovered that OpenGL is not working when I tested against 3D acceleration feature on my CentOS 6.9 Guest VM.
Initially, the upgrade of Guest Addition to the latest 5.2.1-118918 release via iso file would not work.
GUI Desktop looks okay but web browser like Firefox would never open up. Also, it stayed in memory forever and occupied certain CPU resources. I had to use killall to take those processes out.
With command like glxinfo, it pops up lots of replicated error messages as the subject mentioned above.
The following command would never work until I shut down the VM, turned off 3D acceleration feature and then restart again. Viola! Things work again!
Once 3D acceleration is off, the linux VM behaves as it used to be. But, the thing is I really want to make use of OpenGL for graphic acceleration and so on. Can any VBox expert come out and fix this?
First, I tried Firefox after the upgrade of VBox 5.2 and I could not open up Firefox window at all. Rolling back to previous versions of Firefox would not work either.
Reinstalling Gnome desktop and everything did not help. I almost had to reinstalled the whole system to get things work.
Fortunately, I discovered that OpenGL is not working when I tested against 3D acceleration feature on my CentOS 6.9 Guest VM.
Initially, the upgrade of Guest Addition to the latest 5.2.1-118918 release via iso file would not work.
GUI Desktop looks okay but web browser like Firefox would never open up. Also, it stayed in memory forever and occupied certain CPU resources. I had to use killall to take those processes out.
With command like glxinfo, it pops up lots of replicated error messages as the subject mentioned above.
The following command would never work until I shut down the VM, turned off 3D acceleration feature and then restart again. Viola! Things work again!
Code: Select all
$ glxinfo | grep opengl