Message boards :
Number crunching :
All VM tasks postpone
Message board moderation
Author | Message |
---|---|
Send message Joined: 11 Dec 12 Posts: 2 Credit: 1,087,928 RAC: 0 |
Hello. I'm having an issue where all VM tasks are returning 'VM Hypervisor failed to enter an online state in a timely fashion' OR "waiting for memory" I'll speak about the first one first: Task manager shows that 'VM Interface' is using about 30% CPU (of an Intel i5-4690, 4 core @ 3.5GHz), at around the 10 to 20 minute mark, it will pause with the above not timely fashion error. The second one, I'm not sure what sort of 'memory' it is waiting for. But when I have noticed it, task manage says there is about 50% left (of an 8GB RAM machine, leaving 4GB to spare). The same error occured with vLHC@HOME, i recently enabled all other tasks on my LHC@Home account, as it was sixtrack only to start with. Can anyone point me in the direction of what is wrong here? 4GB spare seems quite a lot at least in terms of RAM. I've tried updating VirtualBox, no fix. So i've reverted back to the VirtualBox that comes as part of the BOINC install. I've tried restarting the machine too and removing all active VMs and reloading. Full systen spec: Windows 10 Pro, version 1607 Intel i5-4690, 4 core @ 3.5GHz 8GB of RAM (7.84 usable, according to system info window) Over 100GB of spare space on the drive BOINC uses for data storage |
Send message Joined: 10 Apr 14 Posts: 5 Credit: 1,106,142 RAC: 0 |
I can't say exactly what the issue is but i've had the hypervisor error before and i've noticed that it usually has something to do with the set-up of VirtualBox or virtualization. First i would check to make sure that virtualization is enabled on your OS (for Windows10 open the Task Manager, click the "performance" tab, check lower right corner to see if virtualization is "enabled"). I had a Windows update once that disabled virtualization. If that IS the issue you can re-enable it following the instructions here: https://lhcathome.cern.ch/vLHCathome/forum_thread.php?id=1813&postid=20451#20451 If everything is fine with virtualization and no one recommends a better solution you can try my go-to solution for the hypervisor error. Remove the project, uninstall Vbox, search your hard drive for any files/folders called "virtualbox" and delete them. Then restart your PC and reinstall your preferred version of Vbox + extensions. Restart you're PC again and then re-add the project (make sure you sign-in with your existing acct so you don't lose your credits). When the project is re-added it will re-download the VM and all the necessary stuff. That has always worked for me with the hypervisor error. Also make sure that your version of Vbox isn't too new. I'm using 5.1.4 but use what-ever version has worked for you in the past. Hopefully that will help. |
Send message Joined: 27 Sep 08 Posts: 798 Credit: 644,738,556 RAC: 233,802 |
Looking at your logs from failed task, you need a newer vbox. 5.1.10 the latest works for me. You need at least 5.1 The waiting for memory is either you hit the limit in your boinc settings or you really have run out of ram. With 8Gb I would stick to the Theory and Sixtrack applications |
Send message Joined: 11 Dec 12 Posts: 2 Credit: 1,087,928 RAC: 0 |
As stated in my first post, i did try upgrading the vbox version and it improved nothing, and reverted back to the BOINC provided version as I assumed that was the defacto "known works" and that's why it was provided. However I have reupdated and, unsurprisingly, The same "failed to respond in a timely fashion". I've doubled checked the RAM usage, and once again task manager is reporting 45 to 55% usage, so still around 4GB free, and BOINC is set to allow up to 90% RAM usage (regardless of idle or not) and to leave at minimum 0.25GB free, so at worst there is 3.75GB going around. |
Send message Joined: 10 Apr 14 Posts: 5 Credit: 1,106,142 RAC: 0 |
You may have updated to too new of a version. Try following my reinstall instructions in the above post and when you get to point where you select a vbox version go here: https://www.virtualbox.org/wiki/Download_Old_Builds_5_1 and try 5.1.0, 5.1.2, or 5.1.4 I can only see 1 errored task for your PC right now but it says that you're running version 5.0.12 and as Toby said above, that may be too old. I also notice from the sterr log that you don't have the vbox extensions installed so it can't connect to the remote desktop. I'm not sure if the extensions are required now but it doesn't hurt to install them. Install the preferred vbox version 1st then vbox usually asks if you want to install extensions (do it). If it doesn't ask then you can download and install them from the same link given above under your preferred version where it says "Extension Pack -> All Platforms" I really do recommend following the reinstall instructions in my first post. Clear our all those old virtualbox files and folders before you reinstall. What have you got to lose? |
©2024 CERN