[Fixed] VBoxClient: Failed to get kernel name (#18428)

[socratis]

Done, [Fixed].

[stes]

I confirm that I tested (with display VBoxVGA) and the issue (=Failed to get kernel name) was indeed fixed.

Also everybody in this thread said it was ok to use VBoxVGA ...

I've meanwhile deleted the guest (vm) that I used for testing, but if required I can test it again, or I'll test with a new version or so ...

[stes]

The issue is indeed fixed in 6.0.6 guest additions on a Solaris 11.4 guest with display adapter set to "VBoxVGA".

Code: Select all

stes@pluto:~$ pkg list virtualbox/*
NAME (PUBLISHER)                                  VERSION                    IFO
virtualbox/guest/gnome (local)                    6.0.6-130049               i--
virtualbox/guest/opengl (local)                   6.0.6-130049               i--
virtualbox/guest/vboxguest (local)                6.0.6-130049               i--

and with

Code: Select all

stes@pluto:~$ grep vbox /var/log/Xorg.0.log
[   124.860] (==) Matched vboxvideo as autoconfigured driver 0
[   124.860] (II) LoadModule: "vboxvideo"
[   125.259] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo_drv.so
[   125.297] (II) Module vboxvideo: vendor="Oracle Corporation"
[   125.324] (II) VBoxVideo: guest driver for VirtualBox: vbox

There's no 'failed to get kernel name'.

[michael]

Not fixed in 5.2, you will need to take an Additions test build for that.

https://www.virtualbox.org/wiki/Testbuilds

[stes]

If I downgrade to 5.2.29 testbuild :

Code: Select all

# pkg update -v "virtualbox/guest/*@5.2.29"
            Packages to update:        3
     Estimated space available:  6.19 GB
Estimated space to be consumed: 68.85 MB
       Create boot environment:       No
Create backup boot environment:      Yes
          Rebuild boot archive:       No

Changed packages:
local
  virtualbox/guest/gnome
    6.0.6-130049 -> 5.2.29-130064
  virtualbox/guest/opengl
    6.0.6-130049 -> 5.2.29-130064
  virtualbox/guest/vboxguest
    6.0.6-130049 -> 5.2.29-130064

and then I rebooted the guest.

The host OS is Solaris 11.4 with Virtualbox 6.0.6

Unfortunately the guest is unresponsive after reboot, I can't click anywhere in my VBoxVGA desktop of the guest, after login - it does not seem to do anything. Howver the initial GDM login panel worked fine.

I can ssh into the guest.

This shows:

Code: Select all

stes@pluto:~$ pkg list virtualbox/*
NAME (PUBLISHER)                                  VERSION                    IFO
virtualbox/guest/gnome (local)                    5.2.29-130064              i--
virtualbox/guest/opengl (local)                   5.2.29-130064              i--
virtualbox/guest/vboxguest (local)                5.2.29-130064              i--
stes@pluto:~$ ps -ef | grep VBox
    root   852     1   0 17:11:42 ?           0:00 /usr/bin/VBoxService
    stes  1482     1   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --clipboard
    stes  1483  1482   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --clipboard
    stes  1488     1   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --display
    stes  1489  1488   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --display
    stes  1491     1   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --seamless
    stes  1492  1491   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --seamless
    stes  1494     1   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --draganddrop
    stes  1495  1494   0 17:13:56 ?           0:00 /usr/bin/VBoxClient --draganddrop

Shouldn't I change the host Virtualbox to 5.2.29 ?

Is it supported at all to run host 6.0.6 with guest additions 5.2.29 ?

[michael]

6.0.6 does contain the fix, it is just 5.2.28 which does not. If you are already using 6.0.6 you can just continue with that.

[stes]

If I downgrade the host software from 6.0.6 to 5.2.29 then the guest VM does not start.
The guest VM was created on 6.x.

I have to disable USB 2.0 support (this is indicated/suggested by the error).

Then the VM starts fine. With Display Adapter set to VBoxVGA, and with guest additions 5.2.29 installed (that match the version of the host software), then all is fine, and there is no "Failed to get kernel name" notification.

So the issue seems also fixed in 5.2.29.

I'm always impressed by the ease of installing/upgrading VirtualBox ....