Message boards :
Questions and problems :
BOINC client not detecting VirtualBox installation
Message board moderation
Author | Message |
---|---|
Send message Joined: 5 Oct 06 Posts: 5082 |
Check to see if a line <dont_use_vbox>1</dont_use_vbox> or <dont_use_vbox/> has been created in configuration file cc_config.xml It's a long shot, but at one time the BOINC client created that value to save repeated error messages when things went wrong. |
Send message Joined: 29 Aug 05 Posts: 15483 |
You are right that BOINC can be too busy at startup to detect things like VirtualBox and GPUs. The solution is to use the sleep command on the Boinc process for N seconds, where N is your wanted wait time. You can read through https://boinc.berkeley.edu/forum_thread.php?id=12946 to see if that helps (depending on if you sue systemd or not though) |
Send message Joined: 29 Aug 05 Posts: 15483 |
I didn't offer the delay_start option in cc_config because it delays the starting of science applications only. It may help, but I doubt it because it's the whole hypervisor that isn't detected as I understand. Since the science applications run in that hypervisor, delay starting them doesn't help because they won't start anyway without the hypervisor. (if there are science applications already available) But it's the same here, BOINC seems to start before VirtualBox is ready. Which means that by the time VirtualBox starts, BOINC has already started and it won't try to redetect VirtualBox. So delay starting BOINC can fix this. |
Send message Joined: 14 Aug 19 Posts: 55 |
You can check client_state just to be sure it didn't get borked somehow. * Did you try to crunch Projects using VMs in the past while VT-X / AMD-V / VIA-VT was not enabled? Could be that BOINC has kept this in mind! Team USA forum Follow us on Twitter Help us #crunchforcures! |
Send message Joined: 29 Aug 05 Posts: 15483 |
However, if this was the problem a simple restart of the client after system start should solve the problem.But when are you sure that system start has ended? Simply looking at the drive light won't do it. Would be nice to have the ability to recheck for VB or GPUs without having to restart the client similar to re-read config files.Detection of GPUs, coprocessors and VirtualBox is quite a resource intense procedure and we prefer it only happens at BOINC client start. |
Send message Joined: 29 Aug 05 Posts: 15483 |
In that case I would uninstall and reinstall VirtualBox first, to make sure there isn't something wrong with it or its startup scripts. I didn't read it, but are you sure you need VirtualBox? |
Send message Joined: 5 Oct 06 Posts: 5082 |
When the client starts, depending on project work, the client process (BOINC) runs at least 90% busy for minutes.I've recently had a private communication suggesting that, in the author's opinion, the process which reads, parses and sorts into order the tasks in client_state.xml is coded inefficiently, and in particular takes O(nĀ²) to perform the sort. They have coded an alternative procedure, but I am not sufficiently skilled to verify it is fit for purpose in this context. Anybody available with coding skills to committer level like to take this on? |
Send message Joined: 29 Aug 05 Posts: 15483 |
Have you read https://wiki.centos.org/HowTos/Virtualization/VirtualBox? (Although someone should tell them that hard pink is a difficult background!) |
Send message Joined: 29 Aug 05 Posts: 15483 |
ROFLOL š¤£(Although someone should tell them that hard pink is a difficult background!) That's the nicest thing you ever said to me. šš |
Send message Joined: 29 Aug 05 Posts: 15483 |
And thank you for reporting the solution back. I'll see if we need to document this. I've added it to the BOINC manual. Thanks again. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.