Linux kernel 4.5.0

[mike2712]

Hi All,

I am running Opensuse Tumbleweed (a rolling release) as Linux guest on Win 10 host with VirtualBox 5.0.16.

Everything was fine until a recent update from kernel 4.4.3 to 4.5.0. Now the guest will only boot as far as "Login:" on the boot screen, the desktop does not appear.

Is kernel 4.5.0 compatible with VirtualBox? I did try the 5.0.17 GAs but the problem is not resolved (with or without 3D acceleration).

Cheers

[Perryg]

Support for kernel 4.5.* was just added in trunk so I would think that it should be available in the next released version.

Moving to Linux guests.

[mike2712]

Many thanks - and sorry I put the message in the wrong forum!

[mike2712]

Perryg,

Do you know yet when the next release will be available? I would be happy to test any pre-release.

[Perryg]

Test builds are here https://www.virtualbox.org/wiki/Testbuilds
Pay close attention to the revision number. Not sure when they will release the next maintenance version.

[mike2712]

Thanks. I tried 5.0.17 rev 106155, it does not solve the problem. I will try later revisions when available.

[towo2099]

I don't get it.

Code: Select all

towo:Defiant> uname -a
Linux Defiant 4.5.0-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 4.5-2 (2016-03-14) x86_64 GNU/Linux

Code: Select all

towo:Defiant> dkms status
nvidia, 364.12, 4.5.0-towo.1-siduction-amd64, x86_64: installed
vboxhost, 5.0.16, 4.4.5-towo.1-siduction-amd64, x86_64: installed
vboxhost, 5.0.16, 4.5.0-towo.1-siduction-amd64, x86_64: installed

[mike2712]

OK, mine is:

Code: Select all

uname -a
Linux Tweed_XO 4.5.0-1-default #1 SMP PREEMPT Wed Mar 16 17:30:21 UTC 2016 (b2c9ae5) x86_64 x86_64 x86_64 GNU/Linux

dkms status
vboxguest, 5.0.16, 4.4.3-1-default, x86_64: installed
vboxguest, 5.0.16, 4.5.0-1-default, x86_64: installed

Where do I go from there?

[towo2099]

I don't see your problem.
And if your desktop is not starting, you have no problem with kernel and you should realy provide your /var/log/Xorg.0.log.

[mike2712]

Xorg.0.log

(8.65 KiB) Downloaded 122 times

Thanks. I attach the log.

[Perryg]

There are several things that are involved with a newer kernel such as gcc, and virtual video drivers.

• Post /var/log/vboxadd-install.log as an attachment ( from the guest ).

Try reverting to an older kernel at boot time and see if it allows the guest to work, or drop to a tty window and remove the guest additions and then reboot the guest and see if that allows it to properly boot.
Also try enabling or disabling the 3D acceleration in the guest and see what happens.

Note: towo, I don't know that you would even have the same issue at all. You seem to be running a self-compiled kernel and things might be different for you, and are you saying that you are running Opensuse Tumbleweed guest which will also make a huge difference?

[mike2712]

I can confirm that reverting to the older kernel (4.4.3) at boot time permits correct booting to the desktop. With the new kernel (4.5.0) booting stops at the login prompt, and the desktop never appears.

I installed the GAs into the new kernel from the command line. They replaced the existing ones; I assume that this means they were compiled in correctly when the new kernel was installed. Still no complete boot (i.e. to the desktop) but my shared folders are accessible from the command line. I have not tried your suggestion of removing the GAs, since I do not know how to do so. In any case, that would render the shared folders inaccessible.

Changing 3D acceleration off/on has no effect.

I attach two logs, one for each kernel. They are similar except for an error in 4.5.0 ("nm: 'a.out': No such file").

I think I might be wasting your time with this, since you said earlier that support for kernel 4.5.* would become available, implying that VirtualBox 5.0.16 does not support this?

[Perryg]

Code: Select all

nm: 'a.out': No such file

I remember reading a VBox DEV mailing from the opensuse maintainer about this in the last few weeks. Where they talked about the new kernel and also the status of the guest additions now since they are all moving away from running Xorg with root level permission. So since the guest is having the issue it makes sense that the guest additions would be the cause and is indicated in the build log. Add to that you are running an OS that is in constant flux with new unsupported packages can be fun, but you run into these roadblocks.

[mike2712]

So I guess I have to wait (and hope!). Another point: I tried a completely new install of Tumbleweed, this will not even boot as far as the login prompt, even though it should have exactly the same packages installed as my current "old" version.

[Perryg]

even though it should have exactly the same packages installed as my current "old" version.

I'm afraid that might not be true either. It depends on a few things. Packages updated during install, whether the guest additions are included in the install OS, and even the version of VirtualBox used if different than the original install. As for hoping I can say it will be fixed just a matter of time.

I find it much better to build VirtualBox from SVN since these updates and fixes come sometimes months before they are released due to testing, when using pre-released OSes.