Checking VM hypervisor communication failures for BOINC applications

Message boards : Number crunching : Checking VM hypervisor communication failures for BOINC applications

To post messages, you must log in.

AuthorMessage
Markus Elfring

Send message
Joined: 10 Jun 06
Posts: 17
Credit: 3,610,273
RAC: 0
Message 103914 - Posted: 26 Dec 2021, 18:30:57 UTC

I would like to share some computation resources for selected scientific research.
Thus I dare to run an application like “rosetta python projects 1.03 (vbox64)” again together with the software “BOINC 7.19.0” on an openSUSE Tumbleweed system.

But I stumbled on the status message “Moved: Communication with VM Hypervisor failed.” for tasks like the following (for example) so that I got the impression that the desired data processing is not working as expected at the moment.

  • aaai-SAR_pp-mNMABU-AGLY-ACBEN2_pp_8_2756113_1
  • aaqb-SAR-mALA-AMACBEN4-mACPenC12C_pp_5_2805265_1
  • boinc_cages_IL_2728657_84362
  • boinc_cages_IL_2728657_84423



How can remaining open issues be resolved here?

ID: 103914 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
tullio

Send message
Joined: 10 May 20
Posts: 63
Credit: 630,125
RAC: 0
Message 103915 - Posted: 26 Dec 2021, 19:23:32 UTC - in response to Message 103914.  

My Tumbleweed says that it uses BOINC 7.18.1 and is a development version which may not work properly. But I am not running Rosetta@home python on that Linux because it is a Virtual Machine with only 9 GB RAM and only 9.15 GB disk for BOINC.
Tullio
ID: 103915 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Markus Elfring

Send message
Joined: 10 Jun 06
Posts: 17
Credit: 3,610,273
RAC: 0
Message 103921 - Posted: 27 Dec 2021, 12:42:57 UTC


  • How do you think about to achieve any further insights for the program “/var/lib/boinc/projects/boinc.bakerlab.org_rosetta/vboxwrapper_26198_x86_64-pc-linux-gnu”?
  • How should the software components evolve according to information like the following?


/var/lib/boinc/slots/0/stderr.txt:
“…

2021-12-27 13:33:32 (3837): Detected: VirtualBox VboxManage Interface (Version: 6.1.30)
2021-12-27 13:33:38 (3837): Error in host info for VM: -1041038848
Command:
VBoxManage -q list hostinfo 
Output:
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

2021-12-27 13:33:38 (3837): WARNING: Communication with VM Hypervisor failed.

…”
ID: 103921 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : Checking VM hypervisor communication failures for BOINC applications



©2024 University of Washington
https://www.bakerlab.org