Display drivers no-longer load after recent dnf update on Fedora 24

[Louis6321]

VirtualBox Version 5.1.0 r108711 (had the same problem in the latest 5.0.x version, upgraded to see if it would fix the problem - it didn't)
Host: Fedora 24 64bit 16GM RAM
Guest: Windows 10 64bit 2GB RAM
Log file:

Windows 10-2016-07-17-16-57-59.log.zip

(27.7 KiB) Downloaded 97 times

When I boot the Windows guest, it boots up as per normal and then when the desktop would normally show up, it stays black for about 30 seconds and then it finally appears with a notification saying the display drivers couldn't load and that it's using Microsoft's basic drivers.

I've reinstalled guest additions, tried upgrading from the 5.0.x Virtualbox feed to the latest 5.1.0. Didn't fix it.

The problem started since I ran dnf update -y a few days ago (to bring everything in Fedora 24 up to date).

Any help appreciated.
Thanks.

[Louis6321]

Anyone? Any help appreciated.

[Perryg]

It looks like your host GPU driver ( Gallium 0.4 on llvmpipe ) is having an issue. Since your issue started after an update to the OS, have you tried re-compiling the VirtualBox kernel modules?

[Louis6321]

Since your issue started after an update to the OS, have you tried re-compiling the VirtualBox kernel modules?

Like this?

Code: Select all

[louis@louis-f24 ~]$ sudo /sbin/rcvboxdrv setup
vboxdrv.sh: Starting VirtualBox services.

That's what I found for recompiling the kernel modules when Googling.
The command completes straight away which makes me dubious it's really doing anything.

I assume I'm running the wrong command?

[Perryg]

Yes that should do it but if not then try installing VirtualBox again from the CLI and see if it reports any errors.

[Louis6321]

Yes that should do it but if not then try installing VirtualBox again from the CLI and see if it reports any errors.

So, as root, I did:

dnf remove VirtualBox-5.1 -y
which removed successfully.

Then I did:
cd /home/louis/Downloads
dnf install VirtualBox-5.1-5.1.0_108711_fedora24-1.x86_64.rpm -y

and that installed fine.
I then installed the VirtualBox Extension Pack.
Then I booted the VM.

Same issue

[Perryg]

As a test does the guest boot if you disable the display 3D and 2D acceleration in the guest settings?

[Louis6321]

As a test does the guest boot if you disable the display 3D and 2D acceleration in the guest settings?

Yes it does.

Interestingly, with both of those disabled, the drivers seem to be semi-working again.
I can go into display prefs in the guest and change the resolution and it actually works.
But I used to be able to simply adjust the size of the window and that would adjust the resolution... that's not working, which is kind of annoying coz I maximise and resize and snap the VM to a side of the screen all day long.

[Perryg]

OK so this is now a Windows 10 on VBox issue and I will move this to the proper section. Someone there that uses Windows can help you better than I.

[Louis6321]

OK so this is now a Windows 10 on VBox issue and I will move this to the proper section. Someone there that uses Windows can help you better than I.

Thanks.

Further investigation reveals I can resize the window up to 1152 x 854. If I drag it further, the guest's resolution doesn't increase any further unless I go into Display Settings in Windows and adjust the resolution manually.
Also, the resizing of the window doesn't trigger a resolution change 100% of the time... I often have to go to View > Auto-Resize Guest Display to kick it into gear.

So I guess the issue is... why isn't resizing working like it normally does and why won't it let me go to max resolution without manually selecting that resolution in Windows?

EDIT: Okay, I realise now the "Auto-resize Guest Display" option in the View menu is actually a "Toggle On/Toggle Off" option. The latest version of VBox seems to be missing a tick or something to indicate that.
So with it turned on I can go up to 1152 x 854 but not any bigger. I used to be able to go bigger without any issue.

EDIT2: With regards to the earlier issue of the display drivers not working, I've narrowed it down to 3D acceleration. The guest loads fine with 2D acceleration only.
The resolution issue in the above edit persists though.

[Louis6321]

Bump. Still unable to auto-resize above 1152 x 854.
Any ideas?

[mpack]

It's a common question. E.g. viewtopic.php?f=7&t=78945

[Louis6321]

It's a common question. E.g. viewtopic.php?f=7&t=78945

Thank you so much. Resolved