virtualbox.org

Update: this issue still exists in VirtualBox 5.0.22.

Original post:

I've seen these symptoms in other topics on this site, but none are identical and none have solutions, so I don't want to hijack someone else's thread with a different problem.

I'm running Linux Mint 17.3 (4.2.0-27 kernel) on VirtualBox 5.0.14 under Windows 10. I uninstalled the VirtualBox v4 guest additions from the guest system and installed the 5.0.14 guest additions. When I log in, it warns me that Cinnamon is running in software rendering mode.

> glxinfo | grep -i opengl
libGL error: pci id for fd 4: 80ee:beef, driver (null)
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)
OpenGL version string: 2.1 Mesa 10.1.3
OpenGL shading language version string: 1.30
OpenGL extensions:

The zipped VBox.log is also attached.

Any help someone can give would be great!

Thanks,
Drew

FIrst, Check to be sure that 3D is enabled under display settings of the Guest, and that you've allocated enough RAM to the video card.

Caught me on that one...twice.

3D was enabled, and I just bumped the video memory from 64MB to 128MB, but it's still not working.

Thanks for the advice though!

- Drew

I have a Mint 17 x64 Cinnamon and I used to get this message, but it got fixed some time ago (5.0.4?). Your kernel is quite different from mine and that begs the question; how did the installation of the Guest Additions go? Everything OK? Could you post your "/var/log/vboxadd-install.log"?

Next it's your logs. I didn't quite like this:

00:00:02.576689 OpenGL Info: Render SPU: GL_VENDOR:   Microsoft Corporation
00:00:02.576699 OpenGL Info: Render SPU: GL_RENDERER: GDI Generic
00:00:02.576703 OpenGL Info: Render SPU: GL_VERSION:  1.1.0

Did you update your host's graphics drivers to the latest and greatest?

For reference, this is what I get on my Mint VM:

uname -a
Linux VB-Mint 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

glxinfo | grep -i opengl
libGL error: pci id for fd 4: 80ee:beef, driver (null)
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string: Humper
OpenGL renderer string: Chromium
OpenGL version string: 2.1 Chromium 1.9
OpenGL shading language version string: 1.20
OpenGL extensions:

socratis wrote:how did the installation of the Guest Additions go?

Replying to myself here, but, I just saw this other thread, and the symptoms are quite similar; compilation problems with Mint 17. This time as the host. The kernel in that case is even newer, but I seem to recall that a newer gcc has to be installed to remedy the problem. Don't have the exact link.

having the same problems -

I am running vbox 5.0.14_105127 upgraded today, on windows 10 64 bit host. Correct guest editions installed. I cant run with 3d acceleration enabled - the display doesn't render clearly. if i disable 3d - it was its not running optimally - but looks a lot cleaner.

i have the 70 MB of video memory assigned- but makes no difference if i go to 128MB or not

is there a know fix for this or this just a known issue pending some future release ?

when i run following i get this (this with no 3d running)

glxinfo | grep -i opengl
libGL error: pci id for fd 4: 80ee:beef, driver (null)
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)
OpenGL version string: 2.1 Mesa 10.1.3
OpenGL shading language version string: 1.30
OpenGL extensions:


and this gives me
/usr/lib/nux/unity_support_test -p
libGL error: pci id for fd 4: 80ee:beef, driver (null)
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)
OpenGL version string: 2.1 Mesa 10.1.3

Not software rendered: no
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

when i cat the log i get this
cat /var/log/vboxadd-install.log
Uninstalling modules from DKMS
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxguest/5.0.14/source ->
/usr/src/vboxguest-5.0.14

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.16.0-38-generic -C /lib/modules/3.16.0-38-generic/build M=/var/lib/dkms/vboxguest/5.0.14/build............
cleaning build area....

DKMS: build completed.

vboxguest:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-38-generic/kernel/misc/

vboxsf.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-38-generic/kernel/misc/

vboxvideo.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-38-generic/kernel/misc/

depmod....

DKMS: install completed.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.

Update: I upgraded to VirtualBox 5.0.18, which promisingly stated "Linux/Solaris Additions: fixed several issues causing Linux/Solatis guests using software rendering when 3D acceleration is available." However, this update made things worse. I ran the update and updated the VirtualBox Additions, and now after login as Cinnamon is starting up, it crashes, stating "Cinnamon just crashed. You are currently running in Fallback Mode. Do you want to restart Cinnamon?" Restarting it just makes it crash again immediately. I have to uncheck 3D acceleration now to run Cinnamon.

I'm attaching my Xorg.0.log. Two promising entries seem to be:

[ 13.899] (II) AIGLX: Screen 0 is not DRI2 capable
[ 13.899] (EE) AIGLX: reverting to software rendering

I didn't see anything regarding the crash, though. Is there a way to turn up the log level? Are there other log files I can check out? I didn't see anything relevant in syslog.

As another data point, I found some forum posts elsewhere that suggested the version of libgl1-mesa-dri that's current for Mint 17.3 (10.1.3-0ubuntu0.6) is the issue, but I tried both downgrading (to 10.1.0-4ubuntu5) and upgrading (to the latest version from the oibaf PPA -- https://launchpad.net/~oibaf/+archive/u ... cs-drivers) and it still crashed on startup. Each time I updated the drivers, I (superstitiously?) rebuilt the guest additions.

Thanks,
Drew

One more thing I just noticed. glxinfo now returns:

> glxinfo
name of display: :0

That's all. Something's really broken now.

(Re the mesa drivers, I snapshotted the VM before I changed any driver versions. I've since reverted to the previously installed standard Mint versions.)

- Drew

Resolved! HP just released a video driver update and it fixed the issue. Good luck to anyone else having this problem, and thanks to those who contributed!

- Drew

DMaz99 wrote:Resolved! HP just released a video driver update and it fixed the issue. Good luck to anyone else having this problem, and thanks to those who contributed!

- Drew

I'm confused. I run both LM17 and LM18 VMs on Windows 10 with Nvidia graphics card.

I never, or haven't for years now, get this message on LM17, but it has always been there with LM18. So I don't get how it could be a video driver problem or why Linux Mint should regress between 17 and 18 to not doing this right.

Do we have a clue?

d

djplayer wrote: I'm confused. I run both LM17 and LM18 VMs on Windows 10 with Nvidia graphics card.
I never, or haven't for years now, get this message on LM17, but it has always been there with LM18. So I don't get how it could be a video driver problem or why Linux Mint should regress between 17 and 18 to not doing this right.
Do we have a clue?

Post the results of the following in the guests terminal as well as the guests log file ( as an attachment )

Your glxinfo shows that you do not have the additions installed or they are not working properly. Or as in you case you are using the repo version of the guest additions.

VirtualBox VM 5.0.26 r108824 win.amd64 (Jul 18 2016 12:51:10) release log
00:00:16.602401 VMMDev: Guest Additions information report: Version 5.0.24 r108355 '5.0.24_Ubuntu'

Fix is to remove the additions you have now and install the official version that came with your VirtualBox install. After you remove the ones you have now use the device tab and insert guest additions which you can then install by terminal. See the guest additions chapter in your users manual for details.

So, Ubuntu, or Vbox, does not keep the distro guest additions up to date? Odd, isn't it?

I'll give that a try.

VirtualBox has no control over the distros version of the guest additions no more than what they do to the distro version of VirtualBox. Open source means they can change things and why we don't support their versions here.