Advanced search

Forums : Technical Support : Communication with VM Hypervisor failed
Message board moderation

To post messages, you must log in.

AuthorMessage
Koppany

Send message
Joined: 2 Nov 07
Posts: 5
Credit: 754,830
RAC: 0
Message 22672 - Posted: 1 Nov 2020, 17:45:47 UTC
Last modified: 1 Nov 2020, 17:47:45 UTC

I had suspended all new work units from C@h for several months, but requested new units this morning to resume participation. The BOINC Manager appeared to download 22 C@h tasks (camb_boinc2docker 2.05), but each task appeared with the subject error message. I am on 64-bit Windows 10 running VirtualBox 6.1.12 which I downloaded and installed bundled with my current BOINC Manager release 7.16.11.

Does anyone have suggestions for troubleshooting or simply solving this problem? Many thanks in advance.

Terry

P.S. I have the vbox.log file, but I don't see a file attachment function here in the forum. Should I simply paste it into the message box?
ID: 22672 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 163
Credit: 7,586,181
RAC: 0
Message 22673 - Posted: 2 Nov 2020, 17:31:55 UTC - in response to Message 22672.  

Please post more details on your preferences, other projects and how many cpu cores are assigned to your camb_boinc2docker task when it is trying to start. Is the message "Postponed: Communication with VM Hypervisor failed" or are your tasks not starting the VM at all?
ID: 22673 · Report as offensive     Reply Quote
Koppany

Send message
Joined: 2 Nov 07
Posts: 5
Credit: 754,830
RAC: 0
Message 22674 - Posted: 3 Nov 2020, 7:01:15 UTC - in response to Message 22673.  
Last modified: 3 Nov 2020, 7:03:48 UTC

Thanks for your questions.

Yes, the full message is: "Postponed: Communication ... failed."

I'm running a few other non-GPU projects on this Intel i5 4-core CPU, namely:

Einstein@home
Rosetta@home
LHC@home
Milkyway@home
World Community Grid

Cheers,
Terry
ID: 22674 · Report as offensive     Reply Quote
Profile Terrified74
Avatar

Send message
Joined: 8 Mar 20
Posts: 2
Credit: 73,867
RAC: 0
Message 22675 - Posted: 3 Nov 2020, 13:36:06 UTC - in response to Message 22672.  

use a older version of virtual box {5x}. It solved my problem.
ID: 22675 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 163
Credit: 7,586,181
RAC: 0
Message 22676 - Posted: 3 Nov 2020, 14:06:11 UTC - in response to Message 22675.  

Versions 5.2 and 6.0 are unsupported as of July 2020 per the virtualbox.org website.

https://www.virtualbox.org/wiki/Downloads

That error message essentially says the computer is to 'busy' to communicate with the boinc virtualbox wrapper in a timely manor. It has happened on all version of Virtual Box but the 5 version it happens a lot less. You can try the forums over at LHC at home as they have a lot more project that use virtual box and the forum is active to see if there are any fixes.
I had that problem when I would have too many VMs running at one time and the data directory was on a conventional hard disk. I use the app_config.xml method to control the number of concurrent tasks along with the number of cpus assigned to each VM. I had to go down to using only 8 cores total and skipping using up to 16 with hyperthreading/SMT on my platform. I can run two VMs of 4 cores each for Cosmology at home but if I allow 3 concurrent tasks, I sometimes see that error. I am on Virtual Box 6.1.16
ID: 22676 · Report as offensive     Reply Quote
Jim1348

Send message
Joined: 17 Nov 14
Posts: 121
Credit: 4,762,002
RAC: 2,243
Message 22677 - Posted: 3 Nov 2020, 17:17:40 UTC - in response to Message 22676.  

Versions 5.2 and 6.0 are unsupported as of July 2020 per the virtualbox.org website.

But this project is totally unsupported. We are on our own.

Use 5.2.x.
ID: 22677 · Report as offensive     Reply Quote
maeax

Send message
Joined: 21 Dec 17
Posts: 28
Credit: 3,346,416
RAC: 16,230
Message 22865 - Posted: 16 Oct 2021, 16:17:29 UTC

2021-10-15 17:29:40 (8584): ERROR: Vboxwrapper lost communication with VirtualBox, rescheduling task for a later time.
ID: 22865 · Report as offensive     Reply Quote

Forums : Technical Support : Communication with VM Hypervisor failed