Communication with VM hypervisor failed (OS X, vbox 4.3)

Everything about the project RNA World
Nachricht
Autor
MLx
Mikrocruncher
Mikrocruncher
Beiträge: 23
Registriert: 21.05.2011 17:49

Communication with VM hypervisor failed (OS X, vbox 4.3)

#1 Ungelesener Beitrag von MLx » 01.11.2015 11:29

After a long time I finally managed to get a WU, but it won't start.
  • Should I have vbox 5 already, or is 4.3 supported primarily?
  • Is there a way to force BOINC to retry execution, or try executing it manually? I suspect OS X update deleted /usr/loca/bin from $PATH. I re-installed vbox and it seems fixed now, how can I check?
stderr.txt:

Code: Alles auswählen

2015-11-01 10:55:59 (1449): vboxwrapper (7.3.26086): starting
2015-11-01 10:55:59 (1449): Feature: Checkpoint interval offset (539 seconds)
2015-11-01 10:55:59 (1449): Feature: Enabling trickle-ups (Interval: 14400.000000)
2015-11-01 10:55:59 (1449): Detected: VirtualBox sh: VBoxManage: command not found
2015-11-01 10:55:59 (1449): Detected: Sandbox Configuration Enabled
2015-11-01 10:55:59 (1449): WARNING: Communication with VM Hypervisor failed.
2015-11-01 10:55:59 (1449): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
vbox_trace.txt:

Code: Alles auswählen

2015-11-01 10:55:59 (1449):
Command: VBoxManage -q list hostinfo 
Exit Code: 0
Output:
sh: VBoxManage: command not found

ChristianB
Admin
Admin
Beiträge: 1920
Registriert: 23.02.2010 22:12

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#2 Ungelesener Beitrag von ChristianB » 01.11.2015 11:35

The longest "later date" is 24h I think. I don't know of a way to shorten this. Can you execute VboxManage in a console? The search paths are hardcoded and may have changed with either an OS X or a vbox update but 4.3 will suffice. Vbox 5 shouldn't work with our current vboxwrapper.

MLx
Mikrocruncher
Mikrocruncher
Beiträge: 23
Registriert: 21.05.2011 17:49

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#3 Ungelesener Beitrag von MLx » 01.11.2015 11:51

OK, I restarted BOINC with all other projects suspended and it did get re-tried immediately.
Re: executing VBoxManage in Terminal - it didn't work before I updated to 4.3.32 just now (I had 4.3.30). IIRC, the executable was only found in vbox's folder under /Applications, not under /usr/local... Now it works in Terminal (it's now under /usr/local/bin), but the same error appears in BOINC. I'll try rebooting the machine just to be sure.

FYI:

Code: Alles auswählen

retbook:2 root# file /usr/local/bin/VBoxManage 
/usr/local/bin/VBoxManage: Bourne-Again shell script text executable
retbook:2 root# find /usr/local/ /Applications/VirtualBox.app/ -name VBoxManage -ls
27837001        8 -rwxr-xr-x    1 root             wheel                  77 15 okt 14:15 /usr/local//bin/VBoxManage
27836877     2384 -rwxr-xr-x    2 root             admin             1216592 15 okt 14:15 /Applications/VirtualBox.app//Contents/MacOS/VBoxManage
EDIT: NOPE, doesn't work even after reboot.

MLx
Mikrocruncher
Mikrocruncher
Beiträge: 23
Registriert: 21.05.2011 17:49

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#4 Ungelesener Beitrag von MLx » 02.11.2015 18:43

Is there anything else I should check/try?

ChristianB
Admin
Admin
Beiträge: 1920
Registriert: 23.02.2010 22:12

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#5 Ungelesener Beitrag von ChristianB » 02.11.2015 18:58

I'm not sure. You can try to use the latest wrapper (which has a new logic to find VBoxManage) from here: https://github.com/BOINC/boinc/releases ... er%2F26178 using anonymous platform. Or cancel and wait until I update the application on the server (probably next weekend) and then wait until you get another task (probably longer). I'm not sure if the first approach works with an existing task or if it cancels the task and only works for tasks that get assigned later.

Rabbit08151

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#6 Ungelesener Beitrag von Rabbit08151 » 05.01.2016 12:56

I'm pretty sure that Christians idea of using the new wrapper will solve the problem. Atlas@home and VirtualLHC had similar issues with vbox 4.3 and 5.0 on OS X platforms which were solved through either implementing the new wrapper into the project (ATLAS) or by using the anonymous platform (VirtualLHC - I think they will implement the new wrapper soon).

My problem is to compile a working app_info.xml for this project.

System specs:

OS X: 10.11 (El Capitan)
vbox: 5.0.12
boinc: 7.6.22

I took the app_info.xml from this posthttp://www.rechenkraft.net/forum/viewto ... fb#p147583 and modified it:

Code: Alles auswählen

<app_info>
<app>
<name>cmsearch3</name>
<user_friendly_name>cmsearch VM (VirtualBox) 1.0.2</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
<name>rnaWorld2GB_x64_2.vdi</name>
</file_info> 
<file_info>
<name>vboxwrapper_26178_x86_64-apple-darwin</name>
<executable/>
</file_info>
<file_info>
<name>cms_vbox_control_1.12</name>
<executable/>
</file_info>
<file_info>
<name>cmsearch_0.05_x86_64-pc-linux-gnu.zip</name>
<executable/>
</file_info>
<file_info>
<name>cmsunzipcpufeat_0.03_x86_64-pc-linux-gnu<name>
<executable/>
</file_info>
<file_info>
<name>cms_vbox_job_1.12.xml<name>
</file_info>
<app_version>
<app_name>cmsearch3</app_name>
<version_num>110</version_num>
<platform>x86_64-apple-darwin</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>3129245061.717257</flops>
<plan_class>vbox64</plan_class>
<api_version>7.3.0</api_version>
<file_prefix>shared</file_prefix>
<file_ref>
<file_name>rnaWorld2GB_x64_2.vdi</file_name>
<open_name>vm_image.vdi</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>vboxwrapper_26178_x86_64-apple-darwin</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cms_vbox_control_1.12</file_name>
<open_name>shared/boinc_app</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>cmsearch_0.05_x86_64-pc-linux-gnu.zip</file_name>
<open_name>shared/cmsearch.zip</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>cmsunzipcpufeat_0.03_x86_64-pc-linux-gnu</file_name>
<open_name>shared/unzip_cpufeat</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>cms_vbox_job_1.12.xml</file_name>
<open_name>vbox_job.xml</open_name>
</file_ref>
<dont_throttle/>
</app_version>
</app_info> 
BOINC complaints about a syntax error as soon as it starts using this app_info.xml. Even deleting the "platform" and "flops" lines still ends in an syntax error.

Would you please mind having a look on the code above in order to get rid of the error and pushing me in the right direction. I would appreciate if some could provide a working app_info.xml if it's not possible to locate the error above. This would finally enable me to participate in this project.

Many thanks for any ideas in advance.

Jacob Klein
Brain-Bug
Brain-Bug
Beiträge: 564
Registriert: 26.07.2013 15:41

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#7 Ungelesener Beitrag von Jacob Klein » 09.01.2016 14:44

A couple things (Note: I'm trying to help, not insult your intelligence. Apologies if you already knew most of what I'm about to say):

1) Please get a tool like WinMerge, and set its compare options to ignore all whitespace, and compare what you had, to what I'm going to post. It'll help you realize the mistakes you made, including:
* not properly closing some of the name tags.
* Missing the <executable/> tag for at least 1 file.

2) Whenever setting up a new anonymous platform, you should get into the habit of copying your client_state.xml file (so you have no risk of messing up the original), and then finding the relevant details inside of the copy, and then copy/pasting the necessary stuff from it, into your app_info.xml file. That way, you won't have any problems like incorrectly closed tags.

3) Below is an app_info.xml I made, for Windows x64... followed by a possible app_info.xml file that might work for you. I have NOT tested either of them. Differences between them are:
* modify the wrapper to be the right platform and version (ie: use vboxwrapper_26178_x86_64-apple-darwin if you want, instead of my vboxwrapper_26167_windows_x86_64.exe... in 2 places in the file)
* use the correct <platform> value (ie: use x86_64-apple-darwin instead of my windows_x86_64)

4) You can always find the latest vboxwrapper versions here: http://boinc.berkeley.edu/dl/?C=M;O=D

I hope this helps you. Again, I haven't tested it, but you were very close. I'm not sure how you'll get it working when no tasks are available, but once you do, you might consider opening a new thread, to explain how to do app_info.xml.

Regards,
Jacob

What I put together, for platform windows_x86_64, using old 26167 vboxwrapper that project uses:

Code: Alles auswählen

<app_info>
<app>
    <name>cmsearch3</name>
    <user_friendly_name>cmsearch VM (VirtualBox) 1.0.2</user_friendly_name>
    <non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
    <name>rnaWorld2GB_x64_2.vdi</name>
</file_info>
<file_info>
    <name>cmsearch_0.05_x86_64-pc-linux-gnu.zip</name>
</file_info>
<file_info>
    <name>cmsunzipcpufeat_0.03_x86_64-pc-linux-gnu</name>
    <executable/>
</file_info>
<file_info>
    <name>cms_vbox_control_1.12</name>
    <executable/>
</file_info>
<file_info>
    <name>vboxwrapper_26167_windows_x86_64.exe</name>
    <executable/>
</file_info>
<file_info>
    <name>cms_vbox_job_1.12.xml</name>
</file_info>
<app_version>
    <app_name>cmsearch3</app_name>
    <version_num>115</version_num>
    <platform>windows_x86_64</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>3916881588.352382</flops>
    <plan_class>vbox64</plan_class>
    <api_version>7.5.1</api_version>
    <file_prefix>shared</file_prefix>
    <file_ref>
        <file_name>rnaWorld2GB_x64_2.vdi</file_name>
        <open_name>vm_image.vdi</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>vboxwrapper_26167_windows_x86_64.exe</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>cms_vbox_control_1.12</file_name>
        <open_name>shared/boinc_app</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cmsearch_0.05_x86_64-pc-linux-gnu.zip</file_name>
        <open_name>shared/cmsearch.zip</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cmsunzipcpufeat_0.03_x86_64-pc-linux-gnu</file_name>
        <open_name>shared/unzip_cpufeat</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cms_vbox_job_1.12.xml</file_name>
        <open_name>vbox_job.xml</open_name>
    </file_ref>
    <dont_throttle/>
</app_version>
</app_info>
What might work for you, for platform x86_64-apple-darwin, using the current newer 26178 wrapper:

Code: Alles auswählen

<app_info>
<app>
    <name>cmsearch3</name>
    <user_friendly_name>cmsearch VM (VirtualBox) 1.0.2</user_friendly_name>
    <non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
    <name>rnaWorld2GB_x64_2.vdi</name>
</file_info>
<file_info>
    <name>cmsearch_0.05_x86_64-pc-linux-gnu.zip</name>
</file_info>
<file_info>
    <name>cmsunzipcpufeat_0.03_x86_64-pc-linux-gnu</name>
    <executable/>
</file_info>
<file_info>
    <name>cms_vbox_control_1.12</name>
    <executable/>
</file_info>
<file_info>
    <name>vboxwrapper_26178_x86_64-apple-darwin</name>
    <executable/>
</file_info>
<file_info>
    <name>cms_vbox_job_1.12.xml</name>
</file_info>
<app_version>
    <app_name>cmsearch3</app_name>
    <version_num>115</version_num>
    <platform>x86_64-apple-darwin</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>3916881588.352382</flops>
    <plan_class>vbox64</plan_class>
    <api_version>7.5.1</api_version>
    <file_prefix>shared</file_prefix>
    <file_ref>
        <file_name>rnaWorld2GB_x64_2.vdi</file_name>
        <open_name>vm_image.vdi</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>vboxwrapper_26178_x86_64-apple-darwin</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>cms_vbox_control_1.12</file_name>
        <open_name>shared/boinc_app</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cmsearch_0.05_x86_64-pc-linux-gnu.zip</file_name>
        <open_name>shared/cmsearch.zip</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cmsunzipcpufeat_0.03_x86_64-pc-linux-gnu</file_name>
        <open_name>shared/unzip_cpufeat</open_name>
        <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cms_vbox_job_1.12.xml</file_name>
        <open_name>vbox_job.xml</open_name>
    </file_ref>
    <dont_throttle/>
</app_version>
</app_info>

Rabbit08151

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#8 Ungelesener Beitrag von Rabbit08151 » 09.01.2016 16:16

Many thanks for your support Jacob.

I used DiffMerge to compare your version with mine and clearly saw my mistakes. Another lesson learned :D .

Never had a closer look in the client_state.xml. Obviously, I can find every bit of info need in there.

BOINC started without errors and I'm waiting now for a WU to work on.

Again: Many thanks for the detailed advise. Much appreciated. :good:

Jacob Klein
Brain-Bug
Brain-Bug
Beiträge: 564
Registriert: 26.07.2013 15:41

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#9 Ungelesener Beitrag von Jacob Klein » 09.01.2016 16:20

You're welcome :)
Maybe Chris will update the applications to use the newer vboxwrappers -- Chris?
I'd LOVE for new work units, to work correctly on VirtualBox 5. The only reason I have to stick with VirtualBox 4, is due to RNA World's old applications.

Benutzeravatar
Michael H.W. Weber
Vereinsvorstand
Vereinsvorstand
Beiträge: 22418
Registriert: 07.01.2002 01:00
Wohnort: Marpurk
Kontaktdaten:

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#10 Ungelesener Beitrag von Michael H.W. Weber » 10.01.2016 13:43

Jacob Klein hat geschrieben:The only reason I have to stick with VirtualBox 4, is due to RNA World's old applications.
...except if you also participate in ATLAS@home, which, at least so far, always required older versions than those we use at RNA World. But this just as a side remark...

The upgrade of the wrapper to accomodate the latest VirtualBox version is on Christian's to do list.

Michael.
Fördern, kooperieren und konstruieren statt fordern, konkurrieren und konsumieren.

http://signature.statseb.fr I: Kaputte Seite A
http://signature.statseb.fr II: Kaputte Seite B

Bild Bild Bild

MLx
Mikrocruncher
Mikrocruncher
Beiträge: 23
Registriert: 21.05.2011 17:49

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#11 Ungelesener Beitrag von MLx » 18.01.2016 17:59

Is there any information regarding what it the cause of this issue, and how does the new vboxwrapper address it?

As I see it, the vboxwrapper binary is trying to run VBoxManage with no path specified, assuming the it is in PATH (the environment variable). Well guess what - it isn't, even if the user can run VBoxManage in their Terminal.
Apparently, the PATH which boinc (the client daemon), as well as any boinc project executables get, does not include /usr/local/bin, which is where my VBoxManage is located. (The PATH variable in terminal does contain the local directories, which is why it works there)
sudo ps -wwE -p $(pgrep boinc)
PID TTY TIME CMD
73751 ?? 3:47.97 /Applications/BOINCManager.app/Contents/Resources/boinc --redirectio --launched_by_manager TMPDIR=/var/folders/pb/l_xrrcsx7z760w3n0wqd64nr0000gn/T/ __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0 HOME=/Users/user1 SHELL=/bin/bash Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.kAwhoJFnZw/Render SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.VaE0nHJ0pz/Listeners PATH=/usr/bin:/bin:/usr/sbin:/sbin LOGNAME=user1 DISPLAY=/private/tmp/com.apple.launchd.4HMC0bjNCd/org.macosforge.xquartz:0 XPC_SERVICE_NAME=0 USER=user1 XPC_FLAGS=0x0
I don't know, but this look like a boinc-client issue to me (is there a reason why local is omitted from PATH?). I'll try to work around the issue by linking to vboxwrapper from /usr/bin directly, but that's hardly a viable solution for everyone. :-?

ChristianB
Admin
Admin
Beiträge: 1920
Registriert: 23.02.2010 22:12

Re: Communication with VM hypervisor failed (OS X, vbox 4.3)

#12 Ungelesener Beitrag von ChristianB » 23.01.2016 18:27

I updated the vboxwrapper to the latest version for all platforms. You can try to get another task and it should use version 1.16 of the cmsearch VM app (which has the new wrapper).

Antworten

Zurück zu „RNA World Discussions (english)“