This may or may not be helpful, but I recently had VirtualBox fail to run. I had an older version, and couldn’t get the kernel module to rebuild. I forget what it said to run as root, but it didn’t exist on my machine. I had originally installed from the VirtualBox web site rather than Yast. So I tried the “Yast” way, that had the same failure, just a different thing to run to create the kernel module - and that wasn’t on my machine either! I gave up, uninstalled that and installed the newest one from the VB web site. That worked fine, and when I selected the Guest Additions, it offered to install it from VirtualBox, so I did that. Now it works again. The VB package was unsigned, though, so I clicked “ignore” and crossed my fingers. Luckily, it works. I never could get the one in Yast to work on any version of openSuse, for some reason. You could try this as a last resort, if nothing else works. As for me, this is the first thing I’ll do from now on, I don’t have the patience.
Maybe someone has a better solution for you… I needed it to work *now, *so I took a chance.
On Wed, 20 Apr 2016 00:06:01 +0000, HighBloodSugar wrote:
> Maybe someone has a better solution for you… I needed it to work
> -now,
> -so I took a chance.
If you install from the Virtualization repository, it works just fine.
I’ve been using that for years (and promoting it here for years) because
it just works.
As far as I can see there is no problems with the kernel modules themselves. They are there and when I modprobe them everything works as expected. The current version of the Guest Additions pulled in an init script which is referring to a non-existing configuration file. If you have a look on /etc/init.d/vboxadd you can find if test -r $config; then … where $config refers to /var/lib/VboxGuestAdditions/config and this is not there.
The question here is: Why is the config file missing although the Guest Additions came as RPMs from the official LEAP repositories?
So you don’t have to install any VBoxGuestAdditions, since those are already there.
Since /var/lib/VBoxGuestAdditions/config is a result of the install process of VBoxLinuxAdditions.run it is NOT there because the installer didn’t run (and didn’t have to run, as said).
So the answer to “What can I do?” is “Nothing”, just enjoy your install.
Should you need to install a different version of the GuestAdditions for some testing purpose or so, I guess that you should first uninstall the three virtualbox-guest-xxxx, install gcc, make, kernel-default-devel, then cd to the GuestAdditions CD and run as superuser:
sh VBoxLinuxAdditions.run
like we have to do when installing the upstream (Oracle) version of VBox.
Or maybe I’m missing something and don’t understand what your problem is.
Yes, it’s a LEAP guest. That’s exactly what I’m doing since the Guest Additions are part of the distro.
Okay, that sounds comprehensible. But as I have not installed Guest Additions others then from the original LEAP 42.1 repos I don’t understand why the init script checks for the existence of /var/lib/VBoxGuestAdditions/config and breaks if the file is not there. Per definition it cannot be there because the installer was never run.
The init script is definitely part of the rpm package:
Unfortunatelly this doesn’t work because at least vboxsf kernel module is not being loaded because the init script breaks prior to this part because of the missing /var/lib/VBoxGuestAdditions/config.
You don’t have to “install” anything, maybe by doing so you crippled something.
Maybe force-updating virtualbox-guest-tools can restore the config as needed; I don’t have that version installed at the moment, so I can’t be of any specific help there, sorry.
Please make sure that your user (on the guest OS) is part to the “vboxsf” group for shared folders to work.
Hi!
Interesting, -if I interfere with the original OP question or make things more complicated so never mind and sorry for waisting your time.
Host: openSUSE 13.1 server, installed VB 5.0.16 from Oracle.
Guest: LEAP42.1 “server”
I did a zypper dup earlier today on the WM guest and got the following output:
(16/28) Installing: virtualbox-guest-kmp-default-5.0.16_k4.1.15_8-13.1.x86[done]
Additional rpm output:
depmod: ERROR: fstatat(5, vboxsf.ko): No such file or directory
depmod: ERROR: fstatat(5, vboxguest.ko): No such file or directory
depmod: ERROR: fstatat(5, vboxvideo.ko): No such file or directory
warning: file /lib/modules/4.1.12-1-default/updates/vboxvideo.ko: remove failed: No such file or directory
warning: file /lib/modules/4.1.12-1-default/updates/vboxsf.ko: remove failed: No such file or directory
warning: file /lib/modules/4.1.12-1-default/updates/vboxguest.ko: remove failed: No such file or directory
Ok, rebooted and did a check:
..systemctl status vboxadd.service -l
vboxadd.service
Loaded: loaded (/opt/VBoxGuestAdditions-5.0.12/init/vboxadd; enabled)
Active: active (exited) since ons 2016-04-20 12:10:11 CEST; 8min ago
Process: 730 ExecStart=/opt/VBoxGuestAdditions-5.0.12/init/vboxadd start (code=exited, status=0/SUCCESS)
apr 20 12:10:11 opensusemail vboxadd[730]: Starting the VirtualBox Guest Additions ..done
FYI -
It looks like VBox just released v 5.18,
So those who install from Oracle can get it now.
Those who are installing from the OSS can wait until it’s packaged and should show up in our repos.
Guest Additions should be installed consistent with whichever source you use for your base install until the Guest Additions are also packaged and available through the OSS.
Am expecting this should also address the various version inconsistencies when reading the VBox version, Guest Additions, and Extension. (Cross fingers).
Linux kernel version (kernel-default
): 4.1.20-11.1
/lib/modules/4.1.20-11-default/misc — no such file or directory
However, rebooting into 4.1.15 does not solve the problem, as /etc/init.d/vboxadd script that checks for config file pertains to virtualbox-guest-tools package, which is kernel-independent. Moreover, there seems to be no package that provides /var/lib/VBoxGuestAdditions/config.
Uninstall all installed kmp packages and install the latest one again:
sudo zypper rm virtualbox-guest-kmp-default
sudo zypper in virtualbox-kmp-default
The files have been moved to misc only recently, if you also have an older package installed it will still have them in updates. So the kernel might load the older version on boot.
Regarding the config file: I don’t think this would be missing (if it is required). I’ll check where it should come from. But have you tried to just create an empty one?
PS: I had a look, and that config file apparently is only needed to build the kernel modules (with DKMS).
So it is unnecessary (and useless) in the openSUSE packages, which contain prebuilt modules, and no source code.
That part is removed completely from openSUSE’s vboxadd init script though, so that error message shouldn’t even be shown at all…
Actually, there seems to have been a problem with the 5.0.16 update (for Leap 42.1 as well) in particular, apparently that stuff was not removed completely there…
It has been fixed in the devel repo a while ago, an update for Leap has been submitted too.
See 976840 – Shared folder does not work at Leap 42.1 as VirtualBox's guest
You wrote that you use 5.0.6, but that probably was a typo?
5.0.6 was shipped with Leap originally, and does not exist for Kernel 4.1.15, only 4.1.12 (the kernel that was shipped with Leap).
I.e. there is no 5.0.6_k4.1.15_8-13.1, only 5.0.16_k4.1.15_8-13.1…
Yeah, my bad — I typed it all by hand. Sorry for confusion.
Thanks for digging it. Perhaps I better wait until it rolls out in stable repository, as the VM is more or less usable anyway (shared folders is the only function that seems to be missing for me); and I can boot that system on bare metal if necessary.
No problem.
I just checked 5.0.6 only at first, where this part has been removed properly…
Thanks for digging it. Perhaps I better wait until it rolls out in stable repository, as the VM is more or less usable anyway (shared folders is the only function that seems to be missing for me); and I can boot that system on bare metal if necessary.
Well, it should be possible to load the kernel modules manually with modprobe and then mount the shared folders manually.
I.e. something like this:
mount -t vboxsf sharename mountpoint
Running “VBoxService” manually (as root) afterwards should mount them automatically too.
You could of course also change /etc/init.d/vboxadd with a text editor accordingly yourself, it should suffice to just remove this part (starting from line#247) to fix it:
if test -r $config; then
. $config
else
fail "Configuration file $config not found"
fi
test -n "$INSTALL_DIR" -a -n "$INSTALL_VER" ||
fail "Configuration file $config not complete"
But the update shouldn’t take too long I suppose, normally about a week.