Message boards : Number crunching : Communication with VM Hypervisor failed
Message board moderation

To post messages, you must log in.

AuthorMessage
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 17 Mar 15
Posts: 28
Credit: 278,244
RAC: 0
Message 1254 - Posted: 17 Oct 2015, 9:13:26 UTC
Last modified: 17 Oct 2015, 9:14:57 UTC

Hi

I started again CMS-dev on my Mac to see how it goes, and it goes wrong , I find the WU stuck with status "Communication with VM Hypervisor failed" repeating all the time in boinc message log, I canceled one WU yesterday and this morning I find another one in the same status,

the stederr.txt says

2015-10-17 07:35:27 (97085): vboxwrapper (7.7.26175): starting
2015-10-17 07:35:27 (97085): Feature: Checkpoint interval offset (290 seconds)
2015-10-17 07:35:27 (97085): Detected: VirtualBox VboxManage Interface (Version: Unknown)
2015-10-17 07:35:27 (97085): Detected: Sandbox Configuration Enabled
2015-10-17 07:35:28 (97085): WARNING: Communication with VM Hypervisor failed.
2015-10-17 07:35:28 (97085): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.


and the vbox_trace.txt

2015-10-17 07:35:27 (97085):
Command: VBoxManage -q --version
Exit Code: 0
Output:
sh: VBoxManage: command not found

2015-10-17 07:35:27 (97085):
Command: VBoxManage -q list systemproperties
Exit Code: 0
Output:
sh: VBoxManage: command not found

2015-10-17 07:35:28 (97085):
Command: VBoxManage -q list hostinfo
Exit Code: 0
Output:
sh: VBoxManage: command not found


It seems an issue with CMS not being able to run VB, but when starting boinc it finds VB correctly :

12-Oct-2015 20:14:34 [---] VirtualBox version: 4.3.30r101610


I have boinc 7.6.12 (stable version for Mac) with OS X 10.11.

Thanks for your help.
ID: 1254 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Rasputin42
Volunteer tester

Send message
Joined: 16 Aug 15
Posts: 965
Credit: 1,201,381
RAC: 0
Message 1255 - Posted: 17 Oct 2015, 11:59:42 UTC - in response to Message 1254.  

Hi,
as far as i know, there are currently no jobs available.
Please check the CMS jobs on the left and wait, until the job queue is greater than zero.
ID: 1255 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Crystal Pellet
Volunteer tester

Send message
Joined: 13 Feb 15
Posts: 1010
Credit: 591,548
RAC: 0
Message 1256 - Posted: 17 Oct 2015, 16:46:42 UTC - in response to Message 1254.  

Hi

I started again CMS-dev on my Mac to see how it goes, and it goes wrong , I find the WU stuck with status "Communication with VM Hypervisor failed" repeating all the time in boinc message log, I canceled one WU yesterday and this morning I find another one in the same status..
.
.
Thanks for your help.

It could be fixed in vboxwrapper version 26176/26178.
Committed changes in wrapper source code:

"VBOX: Add code to handle search path modification for Linux and Mac.
Something has changed on OS X that prevents /usr/local/bin from being in the default search path. It is when launched from a terminal window, but not when BOINC launches vboxwrapper. I think recent versions of VirtualBox changed where it stores VboxManage on install."
ID: 1256 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 17 Mar 15
Posts: 28
Credit: 278,244
RAC: 0
Message 1257 - Posted: 17 Oct 2015, 20:19:26 UTC

That's a good possibility, my WUs were 26169 and 26175 (is this changing daily ??), so I'll give it another try then, thanks for the info !
ID: 1257 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile ivan
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar

Send message
Joined: 20 Jan 15
Posts: 1093
Credit: 6,893,316
RAC: 0
Message 1261 - Posted: 19 Oct 2015, 14:56:36 UTC - in response to Message 1255.  

Hi,
as far as i know, there are currently no jobs available.
Please check the CMS jobs on the left and wait, until the job queue is greater than zero.

You can be sure I'll let you know when everything is running smoothly again. For the moment you can turn your interests elsewhere if you like.
ID: 1261 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 17 Mar 15
Posts: 28
Credit: 278,244
RAC: 0
Message 1281 - Posted: 21 Oct 2015, 21:52:10 UTC

Gee, I got another 26175, stuck again ! I thought by letting the project open I would only get the latest version WUs... but not.

So canceling the WU and putting CMS on hold for the moment...
ID: 1281 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile ivan
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar

Send message
Joined: 20 Jan 15
Posts: 1093
Credit: 6,893,316
RAC: 0
Message 1282 - Posted: 22 Oct 2015, 0:26:27 UTC - in response to Message 1281.  

Gee, I got another 26175, stuck again ! I thought by letting the project open I would only get the latest version WUs... but not.

So canceling the WU and putting CMS on hold for the moment...

We don't automatically release the latest wrapper, in fact the three species (Windows, Unix, Macintosh) come out at different times due to their being prepared by different people, so we prefer to wait until
a) a problem has been identified, and
b) all three versions have been updated.

I'll ask Laurence if he can update the wrapper.
ID: 1282 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 17 Mar 15
Posts: 28
Credit: 278,244
RAC: 0
Message 1329 - Posted: 25 Oct 2015, 14:41:49 UTC

Just for info, I gave it a try with Atlas again, same error with all WUs, so I decided to install VB 5.0.8 (I was still using latest 4 release), then I couldn't try Atlas again cause no more WUs are available now, so I tried again with CMS and now guess what, it's working fine, I have a WU happily crunching now !
ID: 1329 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Spyder2000

Send message
Joined: 5 Jan 16
Posts: 1
Credit: 4,402
RAC: 0
Message 1563 - Posted: 5 Jan 2016, 22:47:27 UTC

Had same Problem, reinstalled the VM Box to Version 5.0.10. and everything is running fine again.
ID: 1563 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Communication with VM Hypervisor failed


©2020 CERN