Uninstalling modules from DKMS
removing old DKMS module vboxhost version 5.0.20
------------------------------
Deleting module version: 5.0.20
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/5.0.20/source ->
/usr/src/vboxhost-5.0.20
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make -j4 KERNELRELEASE=4.6.0-0.slh.1-aptosid-amd64 -C /lib/modules/4.6.0-0.slh.1-aptosid-amd64/build M=/var/lib/dkms/vboxhost/5.0.20/build....(bad exit status: 2)
Failed to install using DKMS, attempting to install without
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/4.6.0-0.slh.1-aptosid-amd64/build modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0
make[2]: *** Brak reguł do zrobienia obiektu '/tmp/vbox.0/linux/SUPDrv-linux.o', wymaganego przez '/tmp/vbox.0/vboxdrv.o'. Stop.
Makefile:1429: polecenia dla obiektu '_module_/tmp/vbox.0' nie powiodły się
make[1]: *** [_module_/tmp/vbox.0] Błąd 2
Makefile:298: polecenia dla obiektu 'vboxdrv' nie powiodły się
make: *** [vboxdrv] Błąd 2
Hard to say at this point but I would look for missing dependencies. You could try apt-get -f install to see if the dependencies need to be installed and make sure that you have updated the OS to the latest versions of packages. Keep in mind that the OS you have chosen is built on Debian unstable and running a custom kernel, so you may need to ask aptosid for assistance.
Yes, all dependencies are installed. Is there any way to determine if it's problem with virtualbox, or rather kernel headers installation? P.S. I'm on Debian Sid, only kernel is taken from aptosid. Aptosid 4.5.4 has no problems with virtualbox.
giaur500 wrote:Yes, all dependencies are installed. Is there any way to determine if it's problem with virtualbox, or rather kernel headers installation? P.S. I'm on Debian Sid, only kernel is taken from aptosid. Aptosid 4.5.4 has no problems with virtualbox.
So you installed Debian SID and then you installed the aptosid kernel and headers?
You could have an issue with gcc or some other necessary build package not being compatible with the aptosid kernel, but you say aptosid does not have an issue with VirtualBox. Something must be missing from this story that I have not heard yet. Was this a new install, upgrade, other.. How do you know aptosid does not have a problem with VirtualBox or building external modules in general for that matter?
Sorry, I need to clarify what I mean. My system is Debian Sid, all the time. And:
- Debian kernel 4.5 - OK
- Aptosid kernel 4.5 - OK
- Aptosid kernel 4.6 - Failure
So, I had virtualbox working on my Debian Sid, Aptosid kernel 4.5.4. Then, installed aptosid 4.6 kernel and got vboxdrv failure. Still ok on any 4.5 kernel (Debian or Aptosid). Now, there are 2 possible reasons - either 4.6 aptosid kernel headers are broken somehow (4.5 was ok) or virtualbox is unable to handle new 4.6 kernel. It's rather not because of any missing dependencies on my system, module compiles without any problem on 4.5 kernel.
I need to determine, which reason is true, do you have any idea how to do that? Now I reverted to kernel 4.5 again, recompiled module and I'm looking for possible solution for 4.6 kernel. There is no official Debian 4.6 kernel yet, so I have only Aptosid build available.
VirtualBox 5.0.18 (released 2016-04-18)
Linux hosts / guests: Linux 4.5 fixes (bug #15251)
Linux hosts / guests: Linux 4.6 fixes (bug #15298)
While anything is possible I still think your issue is with the guest. I know for a fact that gcc can cause a problem when the newer kernel and it are out of working sync.
I must say (unfortunately), that virtualbox is very unstable on 4.6 kernel. It runs fine 1 of 10 times. I tested official debian 4.6 kernel also, here is the log:
How can you be so sure it is VirtualBox that is having the issues? Below is a snippet from the Debian page about Debian 4.6-1~exp1 (2016-05-17) kernel.
Experimental package
Warning: This package is from the experimental distribution. That means it is likely unstable or buggy, and it may even cause data loss. Please be sure to consult the changelog and other possible documentation before using it.
Perhaps it would be better if you provided empirical data showing the cause. You should also consider that just having a new kernel does not mean that it has the proper packages installed on the machine that actually build and are compatible with said kernel.
Out of curiosity, why are you using these kernels? Is it to try to fix something or do you test kernels and if do why not compile them yourself?
Aptosid devs have fixed their kernel build, so I returned to aptosid kernel. Now I'm on 4.6.1 kernel Vboxdrv compiles, but still virtualbox is very instable on it. I am able to even start my vm (Windows 10 x64) 1/10 times only. Most cases while starting vm, I'm experiencing message "VM critical error" and option to Ignore or shutdown VM.
Sometimes VM starts, but guest system works unstable (for example many weird messages like "app cannot be started, becues it's not initialized properly" while starting Windows Task manager), etc. Can you please examine my first log I posted previously on kernel 4.6?
And again, no any single problem on 4.5 kernel. Note that kernel 4.6.1 is already stable kernel release, so unless nothing is broken in kernel build, I see no reason why should I stick with 4.5, while VB is meant to support 4.6. I can also post fresh log file from failure on aptosid kernel 4.6.1 (if needed).
VBox definitely is not stable on kernel 4.6, I can confirm that: right know I am running kernel 4.5.5, and VBox works perfectly. But as soon as I boot into kernel 4.6.2 and try to use VBox, it crashes. Rebooting into kernel 4.5.5, and VBox works perfectly again. In both cases, I am using the same virtual machines. On kernel 4.5 they work, on kernel 4.6 they crash after a few seconds. Even a newly created VM crashes on kernel 4.6, straight after turning it on. The module does compile on kernel 4.6, but the VMs crash.
This behaviour is repeatable as often as you like it.