Message boards :
Theory Application :
Unable to start VM on some WUs
Message board moderation
Author | Message |
---|---|
Send message Joined: 14 Sep 08 Posts: 43 Credit: 48,616,081 RAC: 47,428 |
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? |
Send message Joined: 2 May 07 Posts: 2071 Credit: 156,181,286 RAC: 105,005 |
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. |
Send message Joined: 15 Jun 08 Posts: 2386 Credit: 222,998,800 RAC: 136,101 |
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. |
Send message Joined: 14 Sep 08 Posts: 43 Credit: 48,616,081 RAC: 47,428 |
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. |
©2024 CERN