[SOLVED] Fedora 22 & VirtualBox 5: no 3D

[sakodak]

I was running Fedora 21 with VirtualBox 5 on a Windows 7 host and had 3D acceleration. There were artifacts, but it worked.

I did a fedup to Fedora 22 and now 3D doesn't work. If I uninstall and re-install the vbox kernel modules, the first time I try to log in to Gnome it hangs on a black screen. I force a reset and I can log in, but with no 3D:

OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits)

The Xorg log reports:

[ 35.355] (EE) AIGLX: reverting to software rendering

If it were up to me I'd put Linux on the hardware and Windows in a VM, as the gods intended, but corporate policy precludes sanity.

Anyway, does anyone else have this working? Is this a known issue? I searched here and the University of Google but didn't find much that was helpful.

I was going to try a clean Fedora 22 install, but I don't have enough disk space on this laptop and corporate security has turned off USB ports. :/

Thanks for reading.

[Perryg]

Code: Select all

OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits)

This means the VirtualBox drivers ( opengl )are not working. When they are you will see chromium/humper instead. I would try installing the new guest additions and then look at /var/log/vboxadd-install.log for details.

[sakodak]

Hi Perry, thanks for responding.

Right now I have the most recent Guest Edition iso, 5.0. I went to multi-user.target and cleaned out all the old versions of VBoxGuestAdditions and reinstalled 5.0. I've done the same with the VirtualBox-guest and akmod-VirtualBox packages from the virtualbox repo. There are different log files, but the same result.

As far as I can tell, the module build goes fine. Two log files were created for this most recent build, vboxadd-install.log and vboxadd-install-x11.log, included below. I can include logs for the repo-based versions if necessary, too.

vboxadd-install.log:

Code: Select all

Uninstalling modules from DKMS
Attempting to install using DKMS

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

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make KERNELRELEASE=4.0.8-300.fc22.x86_64 -C /lib/modules/4.0.8-300.fc22.x86_64/build M=/var/lib/dkms/vboxguest/5.0.0/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/4.0.8-300.fc22.x86_64/extra/

vboxsf.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.0.8-300.fc22.x86_64/extra/

vboxvideo.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.0.8-300.fc22.x86_64/extra/
Adding any weak-modules

depmod...

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

And vboxadd-install-x11.log:

Code: Select all

VirtualBox Guest Additions installation, Window System and desktop setup

[Perryg]

I would like to see the guests log file ( as an attachment )

[sakodak]

I'm really not sure which is relevant, but I put them all in a tarball.

I really appreciate you taking a look. The logs have been anonymized.

vboxlogs.tar.gz

VBox log files

(121.21 KiB) Downloaded 21 times

[Perryg]

The guest log does not show an issue but your hosts startup log is full if "lacks WinVerifyTrust" which indicates a corrupt certificate cache. I am going to move this for now to the Windows host section so you can get more help with the issue.

[sakodak]

This has been solved. Could you please move this back to the fedora area so that others may benefit from this? I'm not concerned with the "winverifytrust" issues at the moment. Unless I should be. If so I'll open up a different thread.

The problem is gdm 3.16. Well, the problem is how gdm 3.16 and virtualbox interact, but the solution for now is to disable gdm and use a different desktop manager. I chose lightdm, but I assume kdm would work as well.

There are many ways to change your DM, but a semi-foolproof way is:

Code: Select all

systemctl enable lightdm.service
systemctl disable gdm.service
systemctl stop gdm.service
systemctl start lightdm.service

Thanks!

Of course, lightdm (or whatever) needs to be installed.

Edit: as of today (7/23/2015) the version of the Guest Additions for Fedora in the virtualbox repo are older than 5.0. I did some testing and the repo based drivers still fail, even with lightdm, in a similar manner. So, unless the version of VirtualBox-guest you're getting from the repo is newer than 4.3.28 then you probably want to use the 5.x ISO image.