Nvidia 337.88 Breaks 3d Acceleration with Virtualbox

[Sakiyurai]

3D acceleration doesn't work with virtualbox after updating to nvidia 337.88 drivers. Can't load VM images with 3d acceleration enabled. Anyone experiencing this issue?

Windows 7 Host, & windows 7 Guest 64bit. Running virtualbox 4.3.12

[xuthan]

I'm getting an error with this driver as well. Strange, because this driver has been a large improvement with other applications in my experience. I'll try to post this on Nvidia forums as well and see how that goes. (I should also add that there are not any issues when using the same vmdk file in VMware Player)

Windows 7 64-bit,
Intel i7 3770k,
16GB RAM,
Nvidia GTX 670

[Sakiyurai]

Update
Tried nvidia 340.43 still doesn't work with virtualbox with 3d acceleration. There hasn't been an update yet for virtualbox.

[Two13]

UPDATE

I installed geforce 334.89 drivers and 3D acceleration works now.

-------

I'm also having this issue using the latest nVidia drivers and VirtualBox.

Win 7 Pro 64bit
3.4ghz i5-3570k
16gb ram
660Ti with nVidia geforce driver 340.52
VirtualBox 4.3.15 r95286 (using 2 cpu, 4gb ram)

Guest Additions seem to be installed but I cannot get it to load with 3d acceleration. I've tried from scratch with various versions of virtualbox, including 4.3.6, 4.3.14, 4.3.12, using the appropriate guest additions for each.

My current test is in latest Ubuntu 64 but I've also tried Linux Mint 17 and latest Kubuntu 64. Here's some info that may be relevant:

Code: Select all

libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.
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, 128 bits)
OpenGL version string: 2.1 Mesa 10.1.3
OpenGL shading language version string: 1.30
OpenGL extensions:

I've tried a bunch of different things and the libGL errors there don't always occur, but the VMware, Inc. and Gallium stuff (software rendering I guess?) is always there.

[xuthan]

Installing the newer Nvidia Drivers 344.11 fixes this issue, or alternatively, use a driver older than 337.xx. Seems like it was a problem on Nvidia's end.

[Sakiyurai]

yup. Just tried 344.11 and 3d acceleration works again. Finally.

[Woolie]

I have an older NVidia card (GeForce 8800 GT) that is not supported by driver 344.11. For others with older cards, this is how I was able to get around the issue:

First make sure that you install driver version 334.89 and verify that 3D acceleration is working with your VM image.

Once it's functioning normally, install driver 340.52 using the custom install. Uncheck the two 3D options (3D Vision Driver and 3D Vision Controller Driver). You can also uncheck PhysX and GeForce experience if the currently installed drivers are newer than what is being installed, if not it's ok to leave them checked. Finish the driver installation.

If everything went OK, your VM image should start normally.

This is only necessary if you have an older card that is not supported by the current driver.

As of this post, the current driver is 344.11.