Virtualbox and a very strange error

[kdeuser]

Hello,

I really am lost on this error as my os is up-to date .

This is the error :

Setting up virtualbox-5.1 (5.1.8-111374~Ubuntu~trusty) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  apt-get install linux-headers-4.4.6-040406-lowlatency
(The last command may fail if your system is not fully updated.)
  apt-get install linux-headers-lowlatency

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
/sbin/ldconfig.real: /usr/lib/i386-linux-gnu/libfontconfig.so.1 is not a symbolic link

Things tried to solve these errors :

- sudo apt-get update
- sudo apt-get upgrade
- sudo apt-get install dkms
- sudo apt-get install build-essentials

Finally,

- apt-get install linux-headers-4.4.6-040406-lowlatency
- apt-get install linux-headers-lowlatency

The last 2 commands tell me that my kernel and headers are up-to date.

I do not know what to do next.

Can somebody show me a solution.

Many thanks.

Note : OS Trusty 14.04

[claydoh]

WHat about this:

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.

Have you done these?

[kdeuser]

Hello,

The readout of :

sudo /sbin/vboxconfig

reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo /sbin/vboxconfig
[sudo] password for reel: 
 Adding system startup for /etc/init.d/vboxdrv ...
   /etc/rc0.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc1.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc6.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc2.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc3.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc4.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc5.d/S20vboxdrv -> ../init.d/vboxdrv
 Adding system startup for /etc/init.d/vboxballoonctrl-service ...
   /etc/rc0.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc1.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc6.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc2.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc3.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc4.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc5.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
 Adding system startup for /etc/init.d/vboxautostart-service ...
   /etc/rc0.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc1.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc6.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc2.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc3.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc4.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc5.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
 Adding system startup for /etc/init.d/vboxweb-service ...
   /etc/rc0.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc1.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc6.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc2.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc3.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc4.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc5.d/S35vboxweb-service -> ../init.d/vboxweb-service
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  apt-get install linux-headers-4.4.6-040406-lowlatency
(The last command may fail if your system is not fully updated.)
  apt-get install linux-headers-lowlatency
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  apt-get install linux-headers-4.4.6-040406-lowlatency
(The last command may fail if your system is not fully updated.)
  apt-get install linux-headers-lowlatency

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  apt-get install linux-headers-4.4.6-040406-lowlatency
(The last command may fail if your system is not fully updated.)
  apt-get install linux-headers-lowlatency
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
reel@BM2LTSR66RBin:/media/hd/home/reel$

Readout of sudo /sbin/vboxconfig :

/var/log/vbox-install.log

Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.

Readout of , apt-get install linux-headers-4.4.6-040406-lowlatency

reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo apt-get install linux-headers-4.4.6-040406-lowlatency
[sudo] password for reel: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-headers-4.4.6-040406-lowlatency is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
reel@BM2LTSR66RBin:/media/hd/home/reel$

reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo apt-get install linux-headers-4.4.6-040406-lowlatency
[sudo] password for reel: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-headers-4.4.6-040406-lowlatency is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
reel@BM2LTSR66RBin:/media/hd/home/reel$

If i go and do the following command without specifying the kernel then the system loads in kernel-3.13 which is no good

I am out of ideas here.

Thanks for helping.

[kdeuser]

Damn, i seem to have made a mess of the os, not able to boot into screen.

The thing that seems to be on my mind is the lack of source for the kernel ?

The kernel is installed , damn it............

[acheron]

Your kernel version string suggests that you are trying to use a kernel from the ubuntu kernel team mainline testing builds repo. Has been a long time since I used those, but it is possible that virtualbox is not recognising the headers as installed via the configs used for those.

Unless you have a very good reason for using those unsupported mainline builds, you shroud really be using the latest kernels from the trusty LTS hardware enablement stack instead.

sudo apt-get install linux-lowlatency-lts-xenial

or

sudo apt-get install linux-generic-lts-xenial

which gives you the xenial 4.4 kernel, backported for trusty

[kdeuser]

Hi,

Installed both lines :

sudo apt-get install linux-lowlatency-lts-xenial

sudo apt-get install linux-generic-lts-xenial

Did not make a whisker of a difference though.

Still refusing to recognize source of kernel.

Thanks for the help.

[acheron]

- apt-get install linux-headers-4.4.6-040406-lowlatency
- apt-get install linux-headers-lowlatency

If you did that, then you won't have matching headers, as they would be for the main archive kernel, not the mainline 4.4.6-040406 ones.

Use both the kernel and headers from one source or the other. Mixing them like that is bound to fail.

If it was me I would get rid of any 4.4.6-040406 kernel and headers you have and just use the ones from the archive. Either the default trusty ones, or the LTS backports.

[sasha]

What doe uname -r say?

[kdeuser]

Hello,

uname -r gives linux-headers-4.4.6-040406-lowlatency.

I have 2 graphics installed one nvidia the other amd radeon.

Nvidia displays desktop etc , the amd displays tv channels ......a tv/satellite receiver.

Both displays have to be in sync ....the vdr part which carries the radeon card has a driver which marriages with the kernel should i go with another kernel then the vdr driver does not work ie, no tv.

The nvidia card also has it`s prefered driver , should i go with another driver then the vdr would not function.



Yes, it is complex and this is a beta version

[sasha]

Hello,

uname -r gives linux-headers-4.4.6-040406-lowlatency.

That seems wrong. uname -r is supposed to return kernel version only, like 4.4.6-040406-lowlatency, it should not reference linux-headers

Can you do this?
cd /lib/modules/$(uname -r)/build/
pwd

For some reason script cannot find kernel sources and based on what you said, they should be installed.