Hello,
I use openSUSE 15.0 and installed VirtualBox 5.2.22 as host.
I also installed openSUSE 15.0 as guest in VirtualBox and installed in the guest additions as root.
If I startup the openSUSE guest as root every thing is fine.
If I startup the openSUSE guest as user I get 4 messages “VBoxClient: failed to connect to the VirtualBox kernel service”
However, after clicking it away it seems to me that every thing is working fine like networking, dynamic screen size, shared folders etc.
It seems to me that some file permissins are not coorect.
Did you solve this problem as I was unable to find something about this on Google or this forum.
thanks in advance
Hi, welcome
Did you add your user to the vboxusers group?
Dear Knurpht,
thanks for your suggestion, I checked it
on the host I am a member of vboxusers
on the guest I am a member of vboxguest and vboxsf, there is no group named vboxusers registered
How do you install Virtualbox?
From openSUSE-OSS Repo?
Dear Sauerland,
thanks, you make a point.
I can not remember how I installed Virtualbox. As the guest did not found the guest-additions it was automatically downloaded, I assume from the Oracle site.
In Yast I see as installed : virtualbox_guest-kmp-default, virtualbox-guest-tools and virtualbox-guest-x11
The package virtualbox is not installed. So it is likely I installed it from the oracle website.
As I do have the vdi files now I can reinstall Virtualbox using the repo.
I let you know the results.
← please ignore my answer from above. I was unable to edit or remove it. →
Dear Sauerland,
thanks, you make a point.
I can not remember how I installed Virtualbox.
In Yast I see as installed : virtual box, virtualbox-host-kmp-default and virtualbox-qt, so I assume I installed it through the repo.
When installing the guest-additions it was not found and it was automatically downloaded, I assume from the Oracle site.
So it is possible that I used virtualbox and the guest-additions from different sources,
??
From host:
post:
zypper se -si virtualbox
From Guest:
post:
zypper se -si virtualbox
From your post,
I assume the error you’re seeing is inside your Guest, and that likely means that something is amiss with your Virtualbox Additions.
If your HostOS installation of Virtualbox was upgraded or your imported your VM from another version of Virtualbox, you probably have a Guest Additions mis-match.
To re-install Guest Additions…
You can first try a “zypper update” to see if your Guest Additions will update automatically
zypper update
If that doesn’t solve your problem, then
Start your Guest
In your Guest Graphical console (Window), under the “Device” menubar option, select the “Insert Guest Additions CD” option and follow the prompts to mount that ISO image…
Then, browse to the location in your File Manager (or command line) and execute the Linux install.
TSU
Dear Sauerland,
I think you ask this question to be able to check that the host and the guest are the same version. I think they are
Host:
S | Name | Type | Version | Arch | Repository
---+-----------------------------+---------+------------------------------------------+--------+--------------------------
i+ | virtualbox | package | 5.2.22-lp150.4.23.1 | x86_64 | openSUSE-Leap-15.0-Update
i | virtualbox-host-kmp-default | package | 5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | virtualbox-host-source | package | 5.2.22-lp150.4.23.1 | noarch | openSUSE-Leap-15.0-Update
i | virtualbox-qt | package | 5.2.22-lp150.4.23.1 | x86_64 | openSUSE-Leap-15.0-Update
guest:
S | Name | Type | Version | Arch | Repository
--+------------------------------+---------+------------------------------------------+--------+--------------------------
i | virtualbox-guest-kmp-default | package | 5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1 | x86_64 | openSUSE-Leap-15.0-Update
i | virtualbox-guest-tools | package | 5.2.22-lp150.4.23.1 | x86_64 | openSUSE-Leap-15.0-Update
i | virtualbox-guest-x11 | package | 5.2.22-lp150.4.23.1 | x86_64 | openSUSE-Leap-15.0-Update
I think the messages are a result of improper privileges when running the guest as user. the error message do not appear when the guest is started as root
(just for clarification, I mentioned it before)
Thanks
Dear TSU2,
I did do your suggestions, but unfortunately without any success. Thanks, we were thinking the same.
Post from host as User:
groups
What Permissions has your VirtualBox Container.
It should be USERNAME/users.
You should only run Virtualbox on the host as User…
Good morning,
The user groups on the host:
ve vboxusers firebird dialout
The directories and files regarding VirtualBox on guest and host are root:root with permission 744, readable by others. I am not sure what you mean with “Virtualbox Container”
I run VirtualBox as user on the host. When openSUSE boots in the guest I can login as root or user. Root login does not give the error messages, user login does.
My conclusion is it has to do with GuestAdditions permissions.
If I reinstall the Guest additions I see:
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.22 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.22 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-default-devel kernel-default-devel-4.12.14-lp150.12.25
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.
Press Return to close this window...
But the kernel development packages on the guest are installed
vbox_os:~ # zypper se -si kernel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+-----------------------+--------+--------------------------
i+ | devel_kernel | pattern | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-1
i+ | kernel-default | package | 4.12.14-lp150.12.25.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | kernel-default | package | 4.12.14-lp150.11.4 | x86_64 | openSUSE-Leap-15.0-1
i | kernel-default-devel | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-devel | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-firmware | package | 20180525-lp150.2.3.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-macros | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-source | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-syms | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | patterns-devel-base-devel_kernel | package | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-1
I will try to uninstall the GuestAdditions and install it gain.
Thanks
Unfortunately, uninstalling the GuestAdditions and installing it gives the same response
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.22 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.22 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-default-devel kernel-default-devel-4.12.14-lp150.12.25
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.
Press Return to close this window...
The guest drivers are installed, why do you build them by doing it manually?
What is the owner and group of the vdi-File on the Host?
Q The guest drivers are installed, why do you build them by doing it manually?
A As one of my many different approaches to get rid of the 4 error messages while booting openSUSE 15.0 as user as VirualBox guest
Q What is the owner and group of the vdi-File on the Host?
A it is ajv:ve the user and its default group
Reding the vboxadd-setup.log of the guest I read;
Building the main Guest Additions module.
Error building the module. Build output follows.
/tmp/vbox.0/Makefile.include.header:141: *** Error: unable to find the headers of the Linux kernel to build against. Specify KERN_VER=<version> (currently 4.12.14-lp150.12.25-default) and run Make again. Stop.
Do you think it might be the difference between currently 4.12.14-lp150.12.25-default and 4.12.14-lp150.12.28.1 as seen by zypper se -si kernel?
Unfortunately the file /tmp/vbox.0/Makefile does not exist, probably deleted by VirtualBox after the install
Q The guest drivers are installed, why do you build them by doing it manually?
A As one of my many different approaches to get rid of the 4 error messages while booting openSUSE 15.0 as user as VirualBox guest
Q What is the owner and group of the vdi-File on the Host?
A it is ajv:ve the user and its default group
Please use Code-Tags for Quotes (quotes) (/quotes) with these ], the small graphics left from Code-Tags #
The Owner of my vdi files are:
USERNAME:users
ls -al /mnt/2TB/Container/VirtualBox/openSUSE15/
total 46736796
drwxr-xr-x 3 xxx users 4096 Dec 15 05:19 .
drwxr-xr-x 29 xxx users 4096 Dec 2 18:45 ..
drwx------ 2 xxx users 4096 Dec 15 04:35 Logs
-rw------- 1 xxx users 5219 Dec 15 05:19 openSUSE15.vbox
-rw------- 1 xxx users 5382 Dec 15 05:19 openSUSE15.vbox-prev
-rw------- 1 xxx users 47858057216 Dec 15 05:19 openSUSE15.vdi
Thanks pointing me to quotes.
Your ls -al pointed me to the intended Container location on the host, on my system it is:
acer:~ # ls -al /mnt/sdc2_vbox/openSUSE\ 15.0\ server/
total 8399016
drwxr-xr-x 4 ajv ve 4096 Dec 16 19:55 .
drwxrwxrwx 5 root root 4096 Dec 12 17:07 ..
drwx------ 2 ajv ve 4096 Dec 16 22:35 Logs
drwx------ 2 ajv ve 4096 Dec 13 12:38 Snapshots
-rw------- 1 ajv ve 4830 Dec 16 19:55 openSUSE 15.0 server.vbox
-rw------- 1 ajv ve 4830 Dec 16 13:10 openSUSE 15.0 server.vbox-prev
-rw------- 1 ajv ve 8602517504 Dec 16 22:42 openSUSE 15.0 server.vdi
not “users” but the user itself “ajv”, I think this is fine
I also checked the "Container on the guest:
vbox_os:~ # ls -al /opt/VBoxGuestAdditions-5.2.22/
total 76
drwxr-xr-x 9 root root 4096 Dec 16 13:05 .
drwxr-xr-x 4 root root 4096 Dec 16 13:05 ..
-rw-r--r-- 1 root root 20516 Nov 8 20:49 LICENSE
drwxr-xr-x 2 root root 4096 Nov 8 20:50 bin
drwxr-xr-x 2 root root 4096 Nov 8 20:49 init
drwxr-xr-x 2 root root 4096 Dec 16 13:05 installer
drwxr-xr-x 2 root root 4096 Nov 8 20:50 lib
drwxr-xr-x 2 root root 4096 Nov 8 20:50 other
-rwxr-xr-x 1 root root 12048 Dec 16 13:05 routines.sh
drwxr-xr-x 2 root root 4096 Nov 8 20:50 sbin
drwxr-xr-x 3 root root 4096 Nov 8 20:49 src
-rwxr-xr-x 1 root root 2988 Dec 16 13:05 uninstall.sh
then I changed the user and group
vbox_os:~ # chown ajv:ve -R /opt/VBoxGuestAdditions-5.2.22/
but the error messages are still there ;-(
Thanks for all your answers, till now it did not went tot to a solution, but I learned a lot of the Linux internals
On the host as root:
zypper in -f virtualbox virtualbox-host-kmp-default virtualbox-qt
On the guest as root:
zypper in -f virtualbox-guest-kmp-default virtualbox-guest-x11 virtualbox-guest-tools
And please update your system, it seems that the last kernel is not installed:
vbox_os:~ # zypper se -si kernel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+-----------------------+--------+--------------------------
i+ | devel_kernel | pattern | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-1
i+ | kernel-default | package | 4.12.14-lp150.12.25.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | kernel-default | package | 4.12.14-lp150.11.4 | x86_64 | openSUSE-Leap-15.0-1
i | kernel-default-devel | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-devel | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-firmware | package | 20180525-lp150.2.3.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-macros | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-source | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-syms | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | patterns-devel-base-devel_kernel | package | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-1
Hello again.
On the host I did:
zypper in -f virtualbox virtualbox-host-kmp-default virtualbox-qt
zypper update
acer:~ # zypper se -si kernel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+-----------------------+--------+--------------------------
i+ | devel_kernel | pattern | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-Oss
i+ | kernel-default | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | kernel-default | package | 4.12.14-lp150.12.25.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-default-devel | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-default-devel | package | 4.12.14-lp150.12.25.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-devel | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-devel | package | 4.12.14-lp150.12.25.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-firmware | package | 20180525-lp150.2.3.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-macros | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-source | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-source | package | 4.12.14-lp150.12.25.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-syms | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-syms | package | 4.12.14-lp150.12.25.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | patterns-devel-base-devel_kernel | package | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-Oss
acer:~ # uname -a
Linux acer 4.12.14-lp150.12.28-default #1 SMP Mon Dec 3 16:46:15 UTC 2018 (b91289f) x86_64 x86_64 x86_64 GNU/Linux
On the guest i did:
zypper in -f virtualbox-guest-kmp-default virtualbox-guest-x11 virtualbox-guest-tools
zypper update
vbox_os:~ # zypper se -si kernel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+-----------------------+--------+--------------------------
i+ | devel_kernel | pattern | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-1
i+ | kernel-default | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | kernel-default | package | 4.12.14-lp150.12.25.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-default-devel | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i | kernel-devel | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-firmware | package | 20180525-lp150.2.3.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-macros | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-source | package | 4.12.14-lp150.12.28.1 | noarch | openSUSE-Leap-15.0-Update
i | kernel-syms | package | 4.12.14-lp150.12.28.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | patterns-devel-base-devel_kernel | package | 20170319-lp150.2.6 | x86_64 | openSUSE-Leap-15.0-1
vbox_os:~ # uname -a
Linux vbox_os 4.12.14-lp150.12.28-default #1 SMP Mon Dec 3 16:46:15 UTC 2018 (b91289f) x86_64 x86_64 x86_64 GNU/Linux
rebuilding the GuestAdditions, now this ik OK, no warnings about the wrong kernel version.
but after reboot, the error messages this was all about, are still there.
I think I run out of options.
drwxr-xr-x 4 ajv ve 4096 Dec 16 19:55 .
drwxrwxrwx 5 root root 4096 Dec 12 17:07 ..
drwx------ 2 ajv ve 4096 Dec 16 22:35 Logs
drwx------ 2 ajv ve 4096 Dec 13 12:38 Snapshots
-rw------- 1 ajv ve 4830 Dec 16 19:55 openSUSE 15.0 server.vbox
-rw------- 1 ajv ve 4830 Dec 16 13:10 openSUSE 15.0 server.vbox-prev
-rw------- 1 ajv ve 8602517504 Dec 16 22:42 openSUSE 15.0 server.vdi
This is a problem for me, my are all USERNAME:users…
Where do you get the group ve?
Dear Sauerland,
I created the group ve myself with a fixed specified group number on all my computers / file server and under all operating systems. It is declared as the default group for me. This makes it easier to transfer files between all these systems