LHC@home

Hello,

after a long fight i get my boinc to accept that VBox is installed.... but now i get compute errors... somebody can help ?
I have another machine with same Linux, same VBox version and same boinc version... i get Atlas units run fine there... but on this machine i get:

2017-02-13 14:23:27 (4371): vboxwrapper (7.7.26196): starting
2017-02-13 14:23:27 (4371): Feature: Checkpoint interval offset (133 seconds)
2017-02-13 14:23:27 (4371): Detected: VirtualBox VboxManage Interface (Version: 5.1.14)
2017-02-13 14:23:32 (4371): Detected: Minimum checkpoint interval (600.000000 seconds)
2017-02-13 14:23:33 (4371): Detected: Heartbeat check (file: 'heartbeat' every 1200.000000 seconds)
2017-02-13 14:23:33 (4371): Successfully copied 'init_data.xml' to the shared directory.
2017-02-13 14:23:47 (4371): Error in registration for VM: -2147467260
Arguments:
VBoxManage -q showvminfo "boinc_7d52b2964d6ee23b" --machinereadable
Output:
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

2017-02-13 14:23:47 (4371): Starting VM. (boinc_7d52b2964d6ee23b, slot#19)
2017-02-13 14:23:47 (4371): Error in start VM for VM: -2135228415
Command:
VBoxManage -q startvm "boinc_7d52b2964d6ee23b" --type headless
Output:
VBoxManage: error: Could not find a registered machine named 'boinc_7d52b2964d6ee23b'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(pszVM).raw(), machine.asOutParam())" at line 572 of file VBoxManageMisc.cpp

2017-02-13 14:23:47 (4371): VM failed to start.
2017-02-13 14:23:47 (4371): Powering off VM.
2017-02-13 14:23:47 (4371): Deregistering VM. (boinc_7d52b2964d6ee23b, slot#19)
2017-02-13 14:23:47 (4371): Removing network bandwidth throttle group from VM.
2017-02-13 14:23:47 (4371): Removing storage controller(s) from VM.
2017-02-13 14:23:47 (4371): Removing VM from VirtualBox.
2017-02-13 14:23:47 (4371): Removing virtual disk drive from VirtualBox.

https://lhcathome.cern.ch/lhcathome/results.php?userid=344411

I'm not a Linux expert, but the message in your post is

VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

Before starting a BOINC task, you could start VirtualBox Manager and a process named VBoxSVC.exe should appear. That's the VirtualBox COM server.
Being already in VirtualBox Manager you could also have a look at the File menu to Virtual Media Manager, whether there are remnants of failed VM's.
You could remove them first before starting new BOINC tasks creating new VM's.

I see also this error... maybe from WU bevore so that Vbox was no more running for the next unit...

2017-02-13 14:08:06 (3637): vboxwrapper (7.7.26196): starting
2017-02-13 14:08:07 (3637): Feature: Checkpoint interval offset (590 seconds)
2017-02-13 14:08:07 (3637): Detected: VirtualBox VboxManage Interface (Version: 5.1.14)
2017-02-13 14:08:07 (3637): Detected: Minimum checkpoint interval (600.000000 seconds)
2017-02-13 14:08:07 (3637): Detected: Heartbeat check (file: 'heartbeat' every 1200.000000 seconds)
2017-02-13 14:08:07 (3637): Successfully copied 'init_data.xml' to the shared directory.
2017-02-13 14:08:08 (3637): Create VM. (boinc_c5fbeddd2ff0dcbc, slot#19)
2017-02-13 14:08:08 (3637): Setting Memory Size for VM. (630MB)
2017-02-13 14:08:08 (3637): Setting CPU Count for VM. (1)
2017-02-13 14:08:09 (3637): Setting Chipset Options for VM.
2017-02-13 14:08:09 (3637): Setting Boot Options for VM.
2017-02-13 14:08:09 (3637): Setting Network Configuration for NAT.
2017-02-13 14:08:09 (3637): Enabling VM Network Access.
2017-02-13 14:08:09 (3637): Disabling USB Support for VM.
2017-02-13 14:08:10 (3637): Disabling COM Port Support for VM.
2017-02-13 14:08:10 (3637): Disabling LPT Port Support for VM.
2017-02-13 14:08:10 (3637): Disabling Audio Support for VM.
2017-02-13 14:08:10 (3637): Disabling Clipboard Support for VM.
2017-02-13 14:08:10 (3637): Disabling Drag and Drop Support for VM.
2017-02-13 14:08:10 (3637): Adding storage controller(s) to VM.
2017-02-13 14:08:11 (3637): Adding virtual disk drive to VM. (vm_image.vdi)
2017-02-13 14:08:11 (3637): Adding VirtualBox Guest Additions to VM.
2017-02-13 14:08:11 (3637): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB)
2017-02-13 14:08:11 (3637): forwarding host port 44432 to guest port 80
2017-02-13 14:08:11 (3637): Enabling remote desktop for VM.
2017-02-13 14:08:12 (3637): Enabling shared directory for VM.
2017-02-13 14:08:12 (3637): Starting VM. (boinc_c5fbeddd2ff0dcbc, slot#19)
2017-02-13 14:08:13 (3637): Error in start VM for VM: 1
Command:
VBoxManage -q startvm "boinc_c5fbeddd2ff0dcbc" --type headless
Output:
VBoxManage: error: The virtual machine 'boinc_c5fbeddd2ff0dcbc' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
Waiting for VM "boinc_c5fbeddd2ff0dcbc" to power on...

2017-02-13 14:08:13 (3637): VM failed to start.
2017-02-13 14:08:13 (3637): Powering off VM.
2017-02-13 14:08:13 (3637): Deregistering VM. (boinc_c5fbeddd2ff0dcbc, slot#19)
2017-02-13 14:08:13 (3637): Removing network bandwidth throttle group from VM.
2017-02-13 14:08:13 (3637): Removing storage controller(s) from VM.
2017-02-13 14:08:13 (3637): Removing VM from VirtualBox.
2017-02-13 14:08:13 (3637): Removing virtual disk drive from VirtualBox.

... VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine ...

Did you execute a kernel update lately?
If so, did you execute a computer restart and a "vboxdrv setup" thereafter?

Sadly, the vbox kernel extensions are not recompiled automatically with kernel updates, so you either need to do as suggested by computezrlme or to remove the vbox package and re-install it again.

i just found this "vboxdrv setup" thing also in Google... so i'll try it this evening... :) thx so far... i'll come back with hopefully good news :)