1) Forums : News : Recent outage explanation (Message 21964)
Posted 12 Oct 2018 by Greg_BE
Post:
I'm out of here. If you can't keep your technology working and create work, then why should I stay on this project?
2) Forums : News : Recent outage explanation (Message 21957)
Posted 10 Oct 2018 by Greg_BE
Post:
My credits are 0 now.
It's been a month since your outage, what's going on?
I guess I should just abandon your project and find another one to take its place. I'll do that this weekend I guess.
3) Forums : News : camb_legacy tasks temporarily suspended (Message 21916)
Posted 20 Aug 2018 by Greg_BE
Post:
From an old timer at LHC::

Try this

Go to regedit

Then HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ DeviceGuard \ Scenarios \ HypervisorEnforcedCode Integrity \ Enabled in the registry to 0

On the left side of that regedit page you will find all of this and slowly scroll through those steps and you will find it pretty easy.

(then you have to reboot of course and I tested this on a Win 10 machine)

This is what got my machine running normal again.
4) Forums : Technical Support : Vbox not working here (Message 21914)
Posted 18 Aug 2018 by Greg_BE
Post:
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.
5) Forums : Technical Support : Vbox not working here (Message 21913)
Posted 18 Aug 2018 by Greg_BE
Post:
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.
6) Forums : Technical Support : Vbox not working here (Message 21911)
Posted 17 Aug 2018 by Greg_BE
Post:
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.
7) Forums : Technical Support : Vbox not working here (Message 21910)
Posted 17 Aug 2018 by Greg_BE
Post:
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.
8) Forums : Technical Support : Vbox not working here (Message 21907)
Posted 15 Aug 2018 by Greg_BE
Post:
Something must be wrong in my MOBO or BIOS. Reinstalled BIOS still no virtualization.

Case closed until I can see my computer doctor.
9) Forums : Technical Support : Vbox not working here (Message 21906)
Posted 14 Aug 2018 by Greg_BE
Post:
My computer doctor is back from vacation in a few days.
In the meantime I will try reinstalling BIOS. That's the last resort.
10) Forums : Technical Support : Vbox not working here (Message 21905)
Posted 14 Aug 2018 by Greg_BE
Post:
New information:

Despite verifying that virtualization is enabled, according to speccy it is not supported.

I also read on the web that hypervisor has to be disabled for VBOX to run. I double checked that. That feature is unchecked and turned off by default.

So by everything normal, virtualization should run. All functions are set to run properly, but something is holding the virtualization hostage.
11) Forums : Technical Support : Vbox not working here (Message 21904)
Posted 14 Aug 2018 by Greg_BE
Post:
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.
12) Forums : Technical Support : Vbox not working here (Message 21902)
Posted 13 Aug 2018 by Greg_BE
Post:
Thanks for that heroic undertaking, and sorry its still not working. I'm not sure I understand why. I've just marked your computer as having extensions enabled by hand on the server, maybe that will force you to get a VM job and the whole thing will get reset, I'm not sure. Let me know if you notice any changes in what's happening.


As of an hour ago, it downloaded a new legacy file.
Guess that's my fate. Might have to post something over on the BOINC project pages and see what they say.
Will check again tomorrow.
Thanks for all the help.


I tried to set up a test machine on VBOX and it spit a bunch of errors back at me. Not sure what all the errors mean. To late at night to research that. Will look in the morning.
13) Forums : Technical Support : Vbox not working here (Message 21901)
Posted 13 Aug 2018 by Greg_BE
Post:
Thanks for that heroic undertaking, and sorry its still not working. I'm not sure I understand why. I've just marked your computer as having extensions enabled by hand on the server, maybe that will force you to get a VM job and the whole thing will get reset, I'm not sure. Let me know if you notice any changes in what's happening.


As of an hour ago, it downloaded a new legacy file.
Guess that's my fate. Might have to post something over on the BOINC project pages and see what they say.
Will check again tomorrow.
Thanks for all the help.
14) Forums : Technical Support : Vbox not working here (Message 21899)
Posted 13 Aug 2018 by Greg_BE
Post:
Thing is, on my BOINC no matter if I remove that and save the file and rename the old file something else, BOINC rewrites <p_vm_extensions_disabled>

So still stuck with legacy tasks. It's almost like VM app is not communicating with BOINC but yet BOINC knows it is there. 8/12/2018 11:10:44 AM | | VirtualBox version: 5.2.16

This looks like your machine:
http://www.cosmologyathome.org/show_host_detail.php?hostid=362858

It states: "CPU does not have hardware virtualization support".

You probably just need to enable it in your motherboard BIOS.


The C@H website will still say this because the underlying problem is that he *has* enabled it but it is not recognized by BOINC (hence receiving no workunits). Once the you get your local client to recognize extensions enabled, this will propagate to the C@H server and you'll then start receiving workunits.


So.....here is what was done.

1)Turned of SVM on BIOS and finished up my existing work for all projects.
2) Unistalled Vbox and wiped registry of all traces
3) Uninstalled BOINC and wiped all traces of it from my system (registry and data files)
4) Restarted system and went into BIOS and enabled SVM
5) Installed Vbox 5.2.16 with extension pack
6) Installed BOINC
7) Altered client state as mentioned earlier BUT BOINC rewrites it with 0 value

So for now I have legacy tasks and I don't see other projects with VM capabilities picking up that I have VBOX. So not really sure what to do. This is a bit above my understanding of BOINC. For that matter I don't know what more can be done other than to leave things alone and let the other projects and this project work through existing tasks and see if what you say is correct.
15) Forums : Technical Support : Vbox not working here (Message 21894)
Posted 12 Aug 2018 by Greg_BE
Post:
The work generation is back after a temporary stoppage. Were you able to get the p_vm_extensions_disabled thing to stop appearing? Another thing you might try there is to also delete everything in the slots/ directory before restarting the BOINC client. In any case, apologies for that bug, I know its extremely annoying and we definitely need to fix it. Unfortunately, despite knowing about it for a while we haven't had the manpower to do it. Its high on my priority list though.



I'll have to burn through all my current work and then wipe BOINC from my system data directory and all. Get back to you on this.
16) Forums : Technical Support : Vbox not working here (Message 21893)
Posted 12 Aug 2018 by Greg_BE
Post:
Thing is, on my BOINC no matter if I remove that and save the file and rename the old file something else, BOINC rewrites <p_vm_extensions_disabled>

So still stuck with legacy tasks. It's almost like VM app is not communicating with BOINC but yet BOINC knows it is there. 8/12/2018 11:10:44 AM | | VirtualBox version: 5.2.16

This looks like your machine:
http://www.cosmologyathome.org/show_host_detail.php?hostid=362858

It states: "CPU does not have hardware virtualization support".

You probably just need to enable it in your motherboard BIOS.


I'll double check that for the 15th time..but maybe I need to cycle it or reset bios all together. I know its enabled.
17) Forums : Technical Support : Vbox not working here (Message 21890)
Posted 12 Aug 2018 by Greg_BE
Post:
At the moment there seems to be problems witn the docker tasks work generation as i cant get many of them
and most of the time the server status page shows none available to send


Didn't think of looking at server status, just assumed it was my system.
Thanks for posting that news.
18) Forums : News : camb_legacy tasks temporarily suspended (Message 21889)
Posted 12 Aug 2018 by Greg_BE
Post:
I see two of your computers do not have have hardware virtualization support, which means they won't be able to receive camb_boinc2docker workunits. You have one which does have support but you need to enable it. Afterwards, you may also need to perform the steps here.



Remove the Cosmology@Home project - did that
Shut down the BOINC client (from Advanced View choose the menu option Advanced->Shutdown Connected Client) - did that
Go to your BOINC folder and edit the file client_state.xml - went there
Remove the line which contains <p_vm_extensions_disabled> {{---BOINC rewrites that line at startup every time. No matter if I save the orginal client_state as a old file and save the edited one as default. I open the file and BOINC has written that line again.
Restart your BOINC client and readd the project - did that. See above.
19) Forums : News : camb_legacy tasks temporarily suspended (Message 21888)
Posted 12 Aug 2018 by Greg_BE
Post:
I'll second your misery.
I've gone round and round with Vbox and even as far as going back to Vbox 5.2.8 and I get nothing but legacy tasks.
20) Forums : Technical Support : Vbox not working here (Message 21885)
Posted 12 Aug 2018 by Greg_BE
Post:
It states this in the FAQ:
Remove the Cosmology@Home project
Shut down the BOINC client (from Advanced View choose the menu option Advanced->Shutdown Connected Client)
Go to your BOINC folder and edit the file client_state.xml
Remove the line which contains <p_vm_extensions_disabled>
Restart your BOINC client and readd the project


Thing is, on my BOINC no matter if I remove that and save the file and rename the old file something else, BOINC rewrites <p_vm_extensions_disabled>

So still stuck with legacy tasks. It's almost like VM app is not communicating with BOINC but yet BOINC knows it is there. 8/12/2018 11:10:44 AM | | VirtualBox version: 5.2.16

So what is going on?

Unchecked legacy and got this again: 8/12/2018 11:35:20 AM | Cosmology@Home | No tasks are available for camb_boinc2docker

Getting a bit pissed off at things..can't figure out where the problem is. Vbox was repaired and reinstalled. System was rebooted, project was removed and added a few times. Same thing over and over.

My system is 64 bit WIn10.


Next 20