LHC and Rosette will not grab any V-Box work and won't tell me why.
I checked all LHC and Rosette FAQs and done some of what it needs and got no were.
I CAN run Mint and DOS under Windows V-Box. So AMD-V is enabled.
If there's a log that I can enable to help me find out why it won't run any V-Box work.
I used the BOINC bundle. Note: Some one told me it could be WSL but uninstalled and that's not the case. Hyper-V is not installed.

3/10/2024 8:58:57 PM | | Starting BOINC client version 7.24.1 for windows_x86_64
3/10/2024 8:58:57 PM | | log flags: file_xfer, sched_ops, task
3/10/2024 8:58:57 PM | | Libraries: libcurl/8.2.1-DEV Schannel zlib/1.2.13
3/10/2024 8:58:57 PM | | Data directory: E:\ProgramData\BOINC
3/10/2024 8:58:57 PM | | Running under account Sandman192
3/10/2024 8:58:57 PM | | CUDA: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 551.76, CUDA version 12.4, compute capability 6.1, 11264MB, 11264MB available, 12064 GFLOPS peak)
3/10/2024 8:58:57 PM | | CUDA: NVIDIA GPU 1: NVIDIA GeForce GTX 980 (driver version 551.76, CUDA version 12.4, compute capability 5.2, 4096MB, 4096MB available, 4979 GFLOPS peak)
3/10/2024 8:58:57 PM | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 551.76, device version OpenCL 3.0 CUDA, 11264MB, 11264MB available, 12064 GFLOPS peak)
3/10/2024 8:58:57 PM | | OpenCL: NVIDIA GPU 1: NVIDIA GeForce GTX 980 (driver version 551.76, device version OpenCL 3.0 CUDA, 4096MB, 4096MB available, 4979 GFLOPS peak)
3/10/2024 8:58:57 PM | | OpenCL: AMD/ATI GPU 0: AMD Radeon(TM) Graphics (driver version 3608.0 (PAL,LC), device version OpenCL 2.0 AMD-APP (3608.0), 14508MB, 14508MB available, 563 GFLOPS peak)
3/10/2024 8:58:59 PM | | Windows processor group 0: 16 processors
3/10/2024 8:58:59 PM | | Host name: Sandman192
3/10/2024 8:58:59 PM | | Processor: 16 AuthenticAMD AMD Ryzen 7 7700X 8-Core Processor [Family 25 Model 97 Stepping 2]
3/10/2024 8:58:59 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 sse4a osvw wdt topx page1gb rdtscp fsgsbase bmi1 smep bmi2
3/10/2024 8:58:59 PM | | OS: Microsoft Windows 11: Professional x64 Edition, (10.00.22631.00)
3/10/2024 8:58:59 PM | | Memory: 27.62 GB physical, 56.62 GB virtual
3/10/2024 8:58:59 PM | | Disk: 2.73 TB total, 2.19 TB free
3/10/2024 8:58:59 PM | | Local time is UTC -5 hours
3/10/2024 8:58:59 PM | | WSL detected:
3/10/2024 8:58:59 PM | | [Ubuntu-22.04] (default): Linux Ubuntu (Ubuntu 22.04.3 LTS [4.4.0-22621-Microsoft])
3/10/2024 8:58:59 PM | | VirtualBox version: 7.0.6
3/10/2024 8:58:59 PM | | Config: use all coprocessors
3/10/2024 8:58:59 PM | | Config: open console window for VirtualBox applications

I get this in my notification "VirtualBox jobs require hardware acceleration support. Your processor does not support the required instruction set".

This is what the VirtualBox manual explains regarding hardware virtualization in section 10.3:
"Oracle VM VirtualBox's 64-bit guest and multiprocessing (SMP) support both require hardware virtualization to be enabled."

Rosetta and LHC@home both send out vbox64 applications, which means their guests are 64-bit.
LHC@home even sends out a multiprocessing application (ATLAS).

Both don't send vbox tasks to a computer that reports hardware virtualization is disabled, like your computer at LHC@home does:
"Virtualbox (7.0.6) installed, CPU does not have hardware virtualization support"


Things you will have to do

1.
Ensure SVM/AMD-V is enabled in the computer's BIOS

2.
Ensure other hypervisors don't conflict with VirtualBox.
Best would be to disable them if they are not required elsewhere.
This mainly applies to Hyper-V which can be disabled running this command as admin:

bcdedit /set hypervisorlaunchtype off

Then reboot.
Be aware that WSL uses certain Hyper-V components.
Your logs show that you use WSL, hence Hyper-V is not completely disabled.

3.
Ensure "<p_vm_extensions_disabled>" is set to "0" in BOINC's client_state.xml.
Detailed instructions can be found here.

4.
In your Windows Defender Security Center disable "Memory integrity" as it also conflicts with VirtualBox's hardware virtualization.

Add #5.
Another possible reason if you run BOINC inside a VirtualBox guest.
To forward hardware virtualization to the guest this option must be ticked in the VirtualBox GUI:
System -> Processor -> Enable Nested VT-x/AMD-V

Wow, from what you told me I have to make my PC variable to attacks to get VM work to work.
Everything you say is not all of this is in the FAQ at all and you giving me all this NEW intonation now seems off.

NEVER HAD A PROBLEM WITH RUNNING ON WIN 10 on Intel. Just made sure the BIOS had Virtual enabled and off it went.
Now I have to go through all the hops to try to get it to run.

The notification that told me VirtualBox jobs require hardware acceleration support doesn't show up any more and nothing in the logs show any errors.
I would think that the log would always come up with the error. Expressly after each startup of BOINC.

OK I'll try it your way and if it still doesn't or does work I'll still go back and change my settings back and NOT make my computer variable and just not use VM work ever again.

Add #5.
Another possible reason if you run BOINC inside a VirtualBox guest.
To forward hardware virtualization to the guest this option must be ticked in the VirtualBox GUI:
System -> Processor -> Enable Nested VT-x/AMD-V

This right here I could not figure out but why can't BOINC do all of that in V-Box?

Well can do find out if it will work since LHC ran out of (ATLAS) work.
And Rosetta python projects I'm guessing is for V-Box is out as well.

Well dam, I can't test if it worked or not.

Of course you can test it, even without getting a task.

This is your computer at LHC@home:
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10835631

It states:
Virtualbox (7.0.6) installed, CPU does not have hardware virtualization support


Now change your local configuration, step by step according to each advice you have been given, reboot, start BOINC and connect to the project (once).

Then check again the computer details page.
as long as the statement from above remains unchanged (and I don't mean the VirtualBox version) the project will not send any VBox tasks.
This makes sense since you (your computer) tells the project you are not able to run those tasks.
So why should they waste them and send any?

And yes, you have been told that a couple of times (see LHC@home) but it looks like you ignore every advice.


Hint.
On the computer details page you must find something like this:
Virtualbox (7.0.14) installed, CPU has hardware virtualization support and it is enabled