Message boards : Theory Application : Unable to start VM on some WUs
Message board moderation

To post messages, you must log in.

AuthorMessage
wujj123456

Send message
Joined: 14 Sep 08
Posts: 6
Credit: 3,215,753
RAC: 13,974
Message 41245 - Posted: 14 Jan 2020, 4:04:58 UTC
Last modified: 14 Jan 2020, 4:09:28 UTC

I checked a few failed tasks and they all failed with messages like this.

2020-01-12 15:31:37 (2138):
Command: VBoxManage -q startvm "boinc_74513d880c5d6ae6" --type headless
Exit Code: 1
Output:
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.
VBoxManage: error: The virtual machine 'boinc_74513d880c5d6ae6' 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_74513d880c5d6ae6" to power on...\


Example failures:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=259134333
https://lhcathome.cern.ch/lhcathome/result.php?resultid=259134354

However, the /dev/vboxdrv exists and the mentioned packages are also installed on the host. The host has valid results for same application as well: https://lhcathome.cern.ch/lhcathome/results.php?hostid=10595991&offset=0&show_names=0&state=0&appid=13

I couldn't find any smoking gun as of why it fails some WUs but not others. Could /dev/vboxdrv temporarily become inaccessible for some reason I should be aware of?
ID: 41245 · Report as offensive     Reply Quote
maeax

Send message
Joined: 2 May 07
Posts: 916
Credit: 33,703,146
RAC: 6,710
Message 41246 - Posted: 14 Jan 2020, 7:16:42 UTC - in response to Message 41245.  

You need to enable AMD-V (In BIOS it is called SVM-Parameter) and
you have to install Virtualbox. A good tip is Yeti's Checklist in Atlas-Message-Folder.
ID: 41246 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jun 08
Posts: 1428
Credit: 73,049,393
RAC: 106,512
Message 41247 - Posted: 14 Jan 2020, 7:43:00 UTC - in response to Message 41245.  

Looks like vboxdrv doesn't match your active kernel.
Did you recently do a kernel update?
In this case vboxdrv must be recompiled either manually or via dkms during a reboot.


BTW:
Be so kind as to mark links as URL when you write a post.
ID: 41247 · Report as offensive     Reply Quote
wujj123456

Send message
Joined: 14 Sep 08
Posts: 6
Credit: 3,215,753
RAC: 13,974
Message 41258 - Posted: 14 Jan 2020, 16:24:38 UTC - in response to Message 41247.  

I configured automatic upgrade, but not automatically reboot. I thought the new kernel and components would only be in effect after I reboot. Let me turn auto update off to ensure the vboxdrv is always in sync with kernel to see if the result improves.
ID: 41258 · Report as offensive     Reply Quote

Message boards : Theory Application : Unable to start VM on some WUs


©2020 CERN