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.

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

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.

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.

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.

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.

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.

Maybe you need to update your BIOS? If it doesn't think you have virtualization, then you don't have it. I expect that BOINC just reports on whether you have the VBox software installed, not necessarily that it is working correctly.

Apparently the Ryzen 5 has some compatibility problems with motherboard virtualization.
http://www.tomshardware.com/answers/id-3640748/virtualization-ryzen.html

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

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.

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.

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.

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.

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.

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.

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.

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.

My computer doctor is back from vacation in a few days.
In the meantime I will try reinstalling BIOS. That's the last resort.

Something must be wrong in my MOBO or BIOS. Reinstalled BIOS still no virtualization.

Case closed until I can see my computer doctor.

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.

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.