Advanced search

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

To post messages, you must log in.

AuthorMessage
7Tonin

Send message
Joined: 3 May 17
Posts: 4
Credit: 289,177
RAC: 564
Message 21407 - Posted: 5 May 2017, 21:14:02 UTC

Hi,
I'm on a fair new computer, and it's first time I try to use boinc with virtualbox
I have activated VT-x in the UEFI firmware (BIOS)

Unfortunately I've got "Communication with VM Hypervisor failed." with camb_boinc2docker 2.04
Otherwise it's ok with camb_legacy 2.17

I have tried with no success to detach/attach once ; to copy an app_config.xml file...

What can help to solve this issue ?

VBox : 5.1.22r115126 virtualbox-5.1.22-1.mga6
Boinc : 7.2.42 (x64) boinc-client-7.2.42-9.mga6
linux : 4.9.26-desktop-1.mga6
ID: 21407 · Report as offensive     Reply Quote
7Tonin

Send message
Joined: 3 May 17
Posts: 4
Credit: 289,177
RAC: 564
Message 21411 - Posted: 6 May 2017, 10:28:58 UTC - in response to Message 21407.  

Until now, my boinc-client was started as boinc user
Despite being member of vboxusers group, boinc user did not manage to communicate with virtualbox... maybe because it has not got any personnal directory where to store its virtual machines ?
# sudo -u boinc VBoxManage -q --version
5.1.22r115126
# sudo -u boinc VBoxManage -q list systemproperties
VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE)
# sudo -u boinc VBoxManage -q list hostinfo
VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE)

As I don't know how to handle this problem, I decided do change the user running boinc, it's now the same user as the user running my graphical session.
systemctl stop boinc-client
In /usr/lib/systemd/system/boinc-client.service
set in [Service]
User=myusername

Then change rights on BOINC directory, boinc logs, and remove lock file
chown -Rf myusername. /home/myusername/BOINC/
/bin/rm -f /var/lib/boinc/lockfile
chmod g+w /var/log/boinc.log
chmod g+w /var/log/boincerr.log

(myusername is member of boinc group)
End with
systemctl daemon-reload
systemctl start boinc-client.service

Now my camb_boinc2docker are running fine. And I can see them in VirtualBox.
This looks as a solution. Maybe you do think others are possible.
ID: 21411 · Report as offensive     Reply Quote
MeGaBeSuNTa

Send message
Joined: 10 Jul 09
Posts: 1
Credit: 1,023,562
RAC: 54
Message 21431 - Posted: 11 May 2017, 15:32:10 UTC - in response to Message 21411.  

Im also having this issue in a i7 PC
All is enabled in Bios but whenever i got a multicore cosmology task (usually 7 cpus - 90%of cpus used), gives me the error - Delayed - Detection of VM Hypervisor failed

I already tried changing the vbox version but always giving me the same.
Im using Windows10_x64 - Creators update with 16gb ram

Anyone who could help???
Thanks
ID: 21431 · Report as offensive     Reply Quote
Profile Marius
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 29 Jun 15
Posts: 466
Credit: 4,276
RAC: 0
Message 21432 - Posted: 11 May 2017, 15:45:37 UTC - in response to Message 21411.  

Until now, my boinc-client was started as boinc user
Despite being member of vboxusers group, boinc user did not manage to communicate with virtualbox... maybe because it has not got any personnal directory where to store its virtual machines ?
# sudo -u boinc VBoxManage -q --version
5.1.22r115126
# sudo -u boinc VBoxManage -q list systemproperties
VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE)
# sudo -u boinc VBoxManage -q list hostinfo
VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE)

As I don't know how to handle this problem, I decided do change the user running boinc, it's now the same user as the user running my graphical session.
systemctl stop boinc-client
In /usr/lib/systemd/system/boinc-client.service
set in [Service]
User=myusername

Then change rights on BOINC directory, boinc logs, and remove lock file
chown -Rf myusername. /home/myusername/BOINC/
/bin/rm -f /var/lib/boinc/lockfile
chmod g+w /var/log/boinc.log
chmod g+w /var/log/boincerr.log

(myusername is member of boinc group)
End with
systemctl daemon-reload
systemctl start boinc-client.service

Now my camb_boinc2docker are running fine. And I can see them in VirtualBox.
This looks as a solution. Maybe you do think others are possible.


Sorry I missed this message earlier. This is really quite interesting and another angle to solving this problem (which unfortunately quite a number of people have) that I had not considered until now. Let me take a look to see if I can reproduce the issue on my computer by switching users and get back to you.
ID: 21432 · Report as offensive     Reply Quote
7Tonin

Send message
Joined: 3 May 17
Posts: 4
Credit: 289,177
RAC: 564
Message 21437 - Posted: 15 May 2017, 22:39:03 UTC - in response to Message 21432.  

Some news : computation are still fine, but I have now a side problem with my msec (I try to guess) because after rebooting, I have to redo the
chmod g+w /var/log/boinc.log
chmod g+w /var/log/boincerr.log
and to add a
chown boinc. /var/log/boinc*
before
systemctl restart boinc-client

By the way, while running, boinc-client seems not too sad to loose the writing rights on /var/log/boinc*
Definitely it needs some improvements...

The other way I'm thinking about, is to find how to give boinc user the ability to run it's own virtualbox, even without home dir... (don't know when I could dig in it, in virtualbox handbook)
ID: 21437 · Report as offensive     Reply Quote
Dirk Broer

Send message
Joined: 17 Feb 13
Posts: 4
Credit: 529,018
RAC: 27
Message 21504 - Posted: 1 Sep 2017, 22:24:36 UTC

VM Hypervisor failed to enter an online state in a timely fashion

I have a box with about 30 Cosmology@Home VM's waiting to get finished.
They're all supposed to be 25 minute jobs, but each has run for 10 minutes -several times- before stopping, each time at about 33%, with this infuriating message.
Each VM gets created with too little video RAM (a mere 2MB), too...
ID: 21504 · Report as offensive     Reply Quote
Dirk Broer

Send message
Joined: 17 Feb 13
Posts: 4
Credit: 529,018
RAC: 27
Message 21506 - Posted: 3 Sep 2017, 7:19:24 UTC

It appears to be firewall related, virtual box doesn't create itself enough rights upon install to connect to the outside world.
ID: 21506 · Report as offensive     Reply Quote
adrianxw
Avatar

Send message
Joined: 25 Aug 07
Posts: 47
Credit: 302,769
RAC: 0
Message 21516 - Posted: 18 Sep 2017, 14:44:13 UTC

I have had this error on an LHC work unit, task stopped with that obscure status after a couple of hours. Updating to the latest VirtualBox and restarting the machine seemed to get it going again.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 21516 · Report as offensive     Reply Quote
KALIK

Send message
Joined: 13 Feb 08
Posts: 1
Credit: 149,237
RAC: 352
Message 21620 - Posted: 10 Jan 2018, 21:13:11 UTC

I had a very similar problem on Linux Mint 18.3 Xfce. I found that there is /var/lib/boinc-client/.config/ directory which had user and group assigned "root". When I changed user and group of this directory and its inner directories and files to user and group "boinc" everything started to work. There are some Virtualbox files in that directory. So it was only a permission problem.
ID: 21620 · Report as offensive     Reply Quote

Forums : Technical Support : Communication with VM Hypervisor failed.