host kernel modules not building (Opensuse LEAP 15.1)

[pattimichelle]

I can't seem to get a definitive answer on the opensuse forum as to why virtualbox doesn't build the kernel modules on my LEAP 15.1 install. I have gcc/gfortran/etc. installed so they *should* build. Can someone suggest how to troubleshoot this problem? I've tried installing both the generic linux ".run" script as well as the ".rpm" package install. The install seems to go OK, but then VB says the kernel modules aren't installed. Is this a known problem with LEAP?

Thank You Very Much,
Michelle

Host: opensuse leap 15.1
Guest: linuxmint

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

I should warn you: VirtualBox provides the hardware, not the guest OS. So we can no more tell you why software you choose to run in the guest does or doesn't do certain things, any more than Dell could tell you.

But, if there's some gross error in the recipe of the VM then the log will tell us that.

[pattimichelle]

Wow, thank you very much for the reply! Console/cat provided, but also attached is the vbox.log file.

Code: Select all

linux-lhkc:/home/patti/Desktop/ISOs # ./VirtualBox-6.1.4-136177-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 6.1.4 r136177 (2020-02-18T17:26:04Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

The installation log file is at /var/log/vbox-install.log.
linux-lhkc:/home/patti/Desktop/ISOs # cat /var/log/vbox-install.log

VirtualBox 6.1.4 r136177 installer, built 2020-02-18T17:26:04Z.

Testing system setup...
Installing VirtualBox to /opt/VirtualBox

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
linux-lhkc:/home/patti/Desktop/ISOs # 

Code: Select all

linux-lhkc:/home/patti/Desktop/ISOs # /sbin/vboxconfig
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
linux-lhkc:/home/patti/Desktop/ISOs #
patti@linux-lhkc:~/VirtualBox> cat /var/log/vbox-setup.log
Building the main VirtualBox module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/4.12.14-lp151.28.36-default/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j8 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
make -C ../../../linux-4.12.14-lp151.28.36 O=/usr/src/linux-4.12.14-lp151.28.36-obj/x86_64/default/. modules
make -C /usr/src/linux-4.12.14-lp151.28.36-obj/x86_64/default KBUILD_SRC=/usr/src/linux-4.12.14-lp151.28.36 \
-f /usr/src/linux-4.12.14-lp151.28.36/Makefile modules
/usr/src/linux-4.12.14-lp151.28.36/Makefile:651: arch/x64/Makefile: No such file or directory
make[3]: *** No rule to make target 'arch/x64/Makefile'.  Stop.
make[2]: *** [Makefile:152: sub-make] Error 2
make[1]: *** [Makefile:24: __sub-make] Error 2
make: *** [/tmp/vbox.0/Makefile-footer.gmk:114: vboxdrv] Error 2
(base) patti@linux-lhkc:~/VirtualBox>