Advanced search

Forums : Technical Support : Vbox not working here
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Greg_BE

Send message
Joined: 16 Jun 13
Posts: 23
Credit: 371,772
RAC: 0
Message 21910 - Posted: 17 Aug 2018, 17:56:22 UTC - in response to Message 21908.  

Just for S&Gs, can you manually install an OS with VBox. Just to separate physical capability from BOINC detection.

Maybe an older version of Vbox. v5.1 something. Or an older version of BOINC.



5.1 is not supported. 5.2.8 is what is supplied by BOINC. Installed 5.2.10 and related extension pack to see if any change will happen. Right now my cache is full of work, so maybe when BOINC tells Cosmo to go look for more work I will see a change. I am highly skeptical of that.


Yes it is. I am running the vbox app here with 5.1.22
http://www.cosmologyathome.org/show_host_detail.php?hostid=309417

If you want help follow the suggestions.


Man, what the hell do you think I have been doing? I've tried everything suggested here and over in LHC where there are some bigger brains. Nothing is working. I've tried regedit's, checked SVM a million times, checked everything and anything to do with virtualization. Nothing works.
ID: 21910 · Report as offensive     Reply Quote
Greg_BE

Send message
Joined: 16 Jun 13
Posts: 23
Credit: 371,772
RAC: 0
Message 21911 - Posted: 17 Aug 2018, 18:04:01 UTC - in response to Message 21909.  

Did you turn on SMT after your BIOS update / reinstall. I know I have to check my ASUS every time I update the BIOS.
I have VBOX 5.2.16 running without problems with the camb_boinc2docker applications only. I did have to set the number of processors to eight or less. I have eight real cores.
Are you running any other virtualization software? You mentioned Hyper-V but I am guessing you are on Windows 10 Home so you shouldn't have that.



SMT is on (automatic I think?) and SVM is enabled but does not trigger virtualization in the CPU. I limited BOINC to 7 cores because 8 cores was causing hang ups and system crashes. This has happened before. All this nonsense that is happening now is after a SSD death and having a new one installed with new Win10. I have had multiple installations of BOINC resulting in new profiles every time. I have gone so far as to remove BOINC, clean the registry, remove the data directory and start from scratch again. Not sure what else to do other than get in contact with my computer repair guy and see what he can do. Nothing suggested here or over at LHC has resulted in any success. All I have had luck with is get out of virtualization not supported into virtualization supported but disabled even though in BIOS it IS enabled. Something is not communicating. BIOS is updated to the latest BIOS. Vbox and extension packs are at 5.2.10 level after I was not sure if 5.2.18was the problem. I have left them at the .10 level for now.
ID: 21911 · Report as offensive     Reply Quote
mmonnin

Send message
Joined: 29 Dec 16
Posts: 48
Credit: 1,785,986
RAC: 173
Message 21912 - Posted: 17 Aug 2018, 23:20:28 UTC - in response to Message 21910.  

Just for S&Gs, can you manually install an OS with VBox. Just to separate physical capability from BOINC detection.

Maybe an older version of Vbox. v5.1 something. Or an older version of BOINC.



5.1 is not supported. 5.2.8 is what is supplied by BOINC. Installed 5.2.10 and related extension pack to see if any change will happen. Right now my cache is full of work, so maybe when BOINC tells Cosmo to go look for more work I will see a change. I am highly skeptical of that.


Yes it is. I am running the vbox app here with 5.1.22
http://www.cosmologyathome.org/show_host_detail.php?hostid=309417

If you want help follow the suggestions.


Man, what the hell do you think I have been doing? I've tried everything suggested here and over in LHC where there are some bigger brains. Nothing is working. I've tried regedit's, checked SVM a million times, checked everything and anything to do with virtualization. Nothing works.


BOINC will recognize many versions of vbox. Just because one comes packaged with BOINC doesn't mean its the only one supported...
ID: 21912 · Report as offensive     Reply Quote
Greg_BE

Send message
Joined: 16 Jun 13
Posts: 23
Credit: 371,772
RAC: 0
Message 21913 - Posted: 18 Aug 2018, 0:05:51 UTC - in response to Message 21912.  
Last modified: 18 Aug 2018, 0:07:00 UTC

Just for S&Gs, can you manually install an OS with VBox. Just to separate physical capability from BOINC detection.

Maybe an older version of Vbox. v5.1 something. Or an older version of BOINC.



5.1 is not supported. 5.2.8 is what is supplied by BOINC. Installed 5.2.10 and related extension pack to see if any change will happen. Right now my cache is full of work, so maybe when BOINC tells Cosmo to go look for more work I will see a change. I am highly skeptical of that.


Yes it is. I am running the vbox app here with 5.1.22
http://www.cosmologyathome.org/show_host_detail.php?hostid=309417

If you want help follow the suggestions.


Man, what the hell do you think I have been doing? I've tried everything suggested here and over in LHC where there are some bigger brains. Nothing is working. I've tried regedit's, checked SVM a million times, checked everything and anything to do with virtualization. Nothing works.


BOINC will recognize many versions of vbox. Just because one comes packaged with BOINC doesn't mean its the only one supported...


Something changed in my computer...no idea what..but for LHC I am now crunching their Vbox tasks. Waiting for 12 or 13 legacy tasks to clear out for Cosmo and see if the virtual stuff kicks in. I have no idea what changed!
BTW..running 5.2.10 and .21 should be .12.
ID: 21913 · Report as offensive     Reply Quote
Greg_BE

Send message
Joined: 16 Jun 13
Posts: 23
Credit: 371,772
RAC: 0
Message 21914 - Posted: 18 Aug 2018, 0:11:54 UTC
Last modified: 18 Aug 2018, 0:30:25 UTC

Virtualbox (5.2.16) installed, CPU has hardware virtualization support and it is enabled

I think a regedit suggested by a LHC user changed things regarding virtualization. Surprising!

And I guess I have been off on which version of Vbox I have been using.
Anyway..now that things seem to be working I am not touching anything for a long time.

One last thing...Speccy does not agree with Cosmo or LHC about virtualization. Still says its disabled...screw Speccy.
ID: 21914 · Report as offensive     Reply Quote
ChristianVirtual

Send message
Joined: 30 Apr 17
Posts: 5
Credit: 1,104,545
RAC: 1
Message 21919 - Posted: 27 Aug 2018, 10:55:55 UTC

I also have some issue with the docker on an 24c/48t Epyc under CentOS

http://www.cosmologyathome.org/result.php?resultid=74548348

Sorry, seems to need to dump all the WU loaded as I have now 90 failed WUs on my belt.
It seems to just wait 600 seconds and then terminate.

VBOx 5.2.16 installed and was working with LHC ...

Any other ideas ?
ID: 21919 · Report as offensive     Reply Quote
Trotador

Send message
Joined: 9 May 17
Posts: 10
Credit: 11,131,899
RAC: 16,918
Message 21920 - Posted: 27 Aug 2018, 18:59:14 UTC - in response to Message 21919.  

I also have some issue with the docker on an 24c/48t Epyc under CentOS

http://www.cosmologyathome.org/result.php?resultid=74548348

Sorry, seems to need to dump all the WU loaded as I have now 90 failed WUs on my belt.
It seems to just wait 600 seconds and then terminate.

VBOx 5.2.16 installed and was working with LHC ...

Any other ideas ?


Try limiting to 8 the quantity of threads used by the VM. Use an app_config.xml file like this.

<app_config>

<app>
<name>camb_boinc2docker</name>
<max_concurrent>6</max_concurrent>
</app>
<app_version>
<app_name>camb_boinc2docker</app_name>
<plan_class>vbox64_mt</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>


</app_config>
ID: 21920 · Report as offensive     Reply Quote
ChristianVirtual

Send message
Joined: 30 Apr 17
Posts: 5
Credit: 1,104,545
RAC: 1
Message 21932 - Posted: 20 Sep 2018, 8:44:17 UTC - in response to Message 21920.  

Thans Trotador,

tried that; fails still the same way ... and no legacy WU ...
:-(
ID: 21932 · Report as offensive     Reply Quote
ChristianVirtual

Send message
Joined: 30 Apr 17
Posts: 5
Credit: 1,104,545
RAC: 1
Message 21933 - Posted: 20 Sep 2018, 8:44:21 UTC - in response to Message 21920.  

Thans Trotador,

tried that; fails still the same way ... and no legacy WU ...
:-(
ID: 21933 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 108
Credit: 5,209,864
RAC: 125
Message 21935 - Posted: 20 Sep 2018, 18:19:23 UTC - in response to Message 21933.  

Do you have the legacy tasks turned off or they won't run either? Is LHC / Virtualbox apps still working correctly? Did you restart Boinc after the creating the app_config.xml file?
ID: 21935 · Report as offensive     Reply Quote
Trotador

Send message
Joined: 9 May 17
Posts: 10
Credit: 11,131,899
RAC: 16,918
Message 21936 - Posted: 20 Sep 2018, 18:25:19 UTC

Christian,
you have your hosts hidden so we can not see the stderr file and try to understand what happens.

Legacy units as I remember were of little utility to the project.
ID: 21936 · Report as offensive     Reply Quote
David Guymer

Send message
Joined: 28 Jan 08
Posts: 4
Credit: 1,158,976
RAC: 589
Message 22031 - Posted: 30 Dec 2018, 0:38:15 UTC - in response to Message 21885.  

I have a similar problem. I have vbox 6.0.0,docker tasks reach .01% done then say they will take a continually longer time to complete. An example of this is a task that before starting was to take 13 minutes suddenly advising that it will take 24 days to complete.
ID: 22031 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 108
Credit: 5,209,864
RAC: 125
Message 22033 - Posted: 30 Dec 2018, 4:33:56 UTC - in response to Message 22031.  

Try setting the number of cpus to half of what is in your machine. Task 2873388 said it had 9 cores allotted and your computer appears to have 12. See the FAQ. You will need to exit and restart client after creating the file.

https://www.cosmologyathome.org/faq.php#limit-cpu
ID: 22033 · Report as offensive     Reply Quote
David Guymer

Send message
Joined: 28 Jan 08
Posts: 4
Credit: 1,158,976
RAC: 589
Message 22035 - Posted: 31 Dec 2018, 10:01:07 UTC

Is c@h compatible with vbox 6.0.0?
ID: 22035 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 108
Credit: 5,209,864
RAC: 125
Message 22037 - Posted: 31 Dec 2018, 17:38:29 UTC - in response to Message 22035.  

I set up an old windows 7 system with VirtualBox 6 and it seems to have problems. I have an app_config.xml set for 2 cores per task. Computer has 4 cores, hyperthreading is off. I had two complete successfully but others are 'Posponed: VM job unmanageable, restarting later (2 CPUS) There doesn't seem to be any spot in progress where it is stopping. All the stuck ones vary.virt

I will leave the machine running. It may be a case where the VBox Wrapper needs to be updated for this version or something.

Do you have the VirtualBox Extensions installed too? I did on this machine.

I just added an exclusion for the Boinc data directory to my AntiVirus just in case that is the problem.
ID: 22037 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 108
Credit: 5,209,864
RAC: 125
Message 22038 - Posted: 31 Dec 2018, 18:19:14 UTC - in response to Message 22037.  
Last modified: 31 Dec 2018, 18:51:39 UTC

I am completing tasks on the computer with VirtualBox 6.

I aborted the work units that were stuck before I made the anti virus exception changes as I didn't know how to completely reset them and they got stuck again.

Are you getting any hints in the stderr.txt file in the project slot?

Link to computer, hopefully. If link doesn't work, my computers show by clicking on my name.
http://www.cosmologyathome.org/show_host_detail.php?hostid=376442
ID: 22038 · Report as offensive     Reply Quote
Profile Coleslaw
Avatar

Send message
Joined: 6 Aug 08
Posts: 19
Credit: 1,952,727
RAC: 13
Message 22099 - Posted: 25 Feb 2019, 20:02:30 UTC

The 3 boxes that I upgraded to vbox v.6 all fail. Most likely needs an updated vbox wrapper like in previous versions. Marius can you confirm?
ID: 22099 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 108
Credit: 5,209,864
RAC: 125
Message 22100 - Posted: 25 Feb 2019, 22:33:28 UTC - in response to Message 22099.  

I don't have any problems running the tasks on Virtual Box 6.0.4 using up to three concurrent, two core tasks on an eight core processor for the Cosmology app. It only runs into trouble if I let it create four concurrent virtual machines / tasks and then you get the lost communication errors and the VM gets postponed for later.

I also am running LHC Atlas tasks set for a single six core task. These both are working well together.

I did notice that vboxwrapper_26200 runs with LOW priority on my Windows 10 while the vboxwrapper_26196 (from LHC / Atlas) runs with BELOW NORMAL. I think what is happening is the computer is just too busy when I attempt to run four concurrent cosmology at home tasks and the priority setting of the wrapper allows for the lost communication error to happen. This error has been happening over multiple Virtual Box versions but, so far, version 6 seems a bit fussier.

Marius, would it be a good idea for you to update the guest additions within the Docker container at this time? It looks like they are a 5.1 version from within the logs, "VBoxService 5.0.16 r105871 (verbosity: 0) linux.amd64 (Mar 4 2016 17:38:55) release log". Can you query your database to see what versions of Virtual Box everyone is running. At least machines currently returning tasks? Virtual Box is now supporting the 5.2 and 6 series and dropped support for previous releases. " Version 5.2 will remain supported until July 2020", from
https://www.virtualbox.org/wiki/Downloads
ID: 22100 · Report as offensive     Reply Quote
Richard

Send message
Joined: 15 May 14
Posts: 1
Credit: 18,056
RAC: 0
Message 22138 - Posted: 27 Mar 2019, 13:05:33 UTC

Hi,

i'm having the exact same problem with every WU on linux, noticed a few days ago.
After i've upgraded to VBox 6.0.4 all WU ended with error.
I can't downgrade VBox at the moment, so it would be great if there is an alternative solution.

OS: openSUSE Leap 15.0
Boinc: 7.8.3
Vbox: 6.0.4 (with vbox ext pack)

Regards
ID: 22138 · Report as offensive     Reply Quote
Previous · 1 · 2

Forums : Technical Support : Vbox not working here