It works, BUT, this is a BIG BUT.

Download from the Oracle site that hosts the S/W, and install it.

I tried a straight download and a download that patched the kernel (like Nvidia drivers do).

BOTH CRASHED UBUNTU 14.04.1 on reboot after a kernel update.

Hdd light flickered intermittently for 10 minutes with Ubuntu not starting, requiring a reinstall of Ubuntu to work around this problem.

A workaround that I have not tested yet, is when a kernel update is ready to happen, uninstall Vbox FIRST!!

It did it again.

Straight download from Oracle site, installed ok.

Atlas and one other app used it.

Ubuntu updated kernel again. On reboot, the text messages that come up when Ubuntu starts were there, but X would not start.

May work fine on Windows, BUT ONTO ON UBUNTU LINUX, AT LEAST NOT WHEN YOU HAVE TO REINSTALL UBUNTU EVERY TIME THE KERNEL UPDATES!!!

Robert,

How did you install VirtualBox? Did you register it with DKMS?

I am running Ubuntu 14.04 with VirtualBox 4.3.12 and have been through several kernel updates without any issues.

When you say that X would not start, are you talking about X-server for video? What kind of error messages are you getting? If you are talking about video, how did you install your video device drivers?

I tried BOTH a straight download and install from the Oracle website AND registration with DKMS. the latest kernel update, 3.13.0.37 (??) applied and when reboot with new kernel, no errors messages, no desktop, wait forever, nothing happens. Just did it on this computer and used Synaptic Package Manager to REMOVE Virtual Box before reboot.

Same problem, no error messages and no desktop, even wait 30 minutes, no desktop.

Ready to reinstall NVidia, manual install and BOINC again.

For me on TWO computers, VBOX stops Ubuntu from restarting once a kernel update happens.

I will try again on this computer, registration with DKMS

DKMS registration of 4.3.10 as that is the only version available.

Latest version from Oracle is 4.3.16

After install of Ubuntu again kernel is 3.13.0.32. .37 will come in 24-48 hours and we will see what happens

Robert,

When you install the NVIDIA drivers, do you also select to register with DKMS?

How to do that?? No option on Nvidia manual install, and no option when installing the Ubuntu drivers.

It crashed AGAIN when Ubuntu restarted after updated kernel to 3.13.0.37

Unless I figure this out soon, VBOX IS DEAD SO FAR AS I AM CONCERNED. It works, but to REINSTALL UBUNTU EVERY TIME UBUNTU UPDATES THE KERNEL IS A NON-STARTER

DKMS when used is later installed, so I must make it FIRST after installation finishes. NVIDIA, I hope with the 340.24 driver I have will register and when 3.13.0.37 kernel comes, all will be well

Ubuntu installed again.

DKMS downloaded and installed FIRST. There are no warnings about this, generally comes as a post-script note [if you want to register your modules with DKMS so that they automatically update when Linux updates kernel]

They make it seem on BOTH Virtual Box and Nvidia that this is NOT necessary.

With NVIDIA, it is not.

It appears MANDATORY for Virtual Box

Will it work to manually install Nvidia drivers AGAIN after DKMS is installed?? This SHOULD register NVIDIA with DKMS so that when kernel updates BOTH get updated, and the system works correctly.

Am I correct in this assumption??

One system is configured with both on DKMS, the other only has VBOX in DKMS and I KNOW that system will CRASH when kernel goes from 3.13.0.37 to something higher.

I will likely find out tomorrow if DKMS on BOTH solves my problem.

What seems to work is to

install dkms first

manual install of NVIDIA drivers (340* or higher)

then install boinc from LocutusOfBorg

sudo apt-get purge virtualbox*

then reboot.

sudo apt-get install virtualbox*

Then vbox apps run cleanly. Without the * some apps will never run

I have yet to get a kernel update to test this, but apps are running on two machines without issue

And at some point, Vbox stops talking to BOINC and the computer must reboot to get the tasks running again.

I suspect that this does NOT happen on Winblows

I can confirm. Vbox stopped talking to the ATLAS application and to get it restarted, Ubuntu had to reboot.

This is not good behavior

And at some point, Vbox stops talking to BOINC and the computer must reboot to get the tasks running again.

I suspect that this does NOT happen on Winblows

I have tried to run Atlas@home using Windows 7 and that is what I experienced. Please note that these tasks should be run with hyper-threading not being enabled. After re-booting, the tasks would sometimes error out as well. Atlas@home has very intensive and demanding tasks being run using virtualization software, and IMHO running highly intensive and demanding applications using virtualization software is never a good idea as problems usually occur that does not end well. Others may disagree.

Hyperthreading enabled???

Have not TOUCHED the VBOX manager.

It happened again. Rebooted this morning and after 6 hours, Atlas stopped running. Several jobs finished, but one got stuck

Opened the manager, but did NOT create a window. The window that SHOULD be there was not. At one point in the last two days, up to 5 ATLAS jobs were running at the same time

On the other machine, 4 Atlas jobs are running, but no window in Oracle Window manager