LHC@home

Maybe all these problems are caused by switching from classic BIOS boot to UEFI .... ??

IBM called it Microchannel in the past,
Microsoft call it TPM (since five Year all Mainboard manufactories produce it so).

There's something up with LHC's tasks not detecting I have virtualisation enabled.

I can't imagine that there is something wrong with the tasks.
The vboxwrapper and vdi-image files aren't changed recently.
It seems that only Windows user are affected and not Linux using VBox.
Could someone with this problem try 1 Rosetta VBox task or a VBox-task from another project?

Perhaps something should be posted somewhere for what is presumably going to affect all Windows users.

We always request to completely disable Hyper-V following the advice given in the VirtualBox forum which also requests to completely disable Hyper-V.
And it's already posted "somewhere".
Google currently has 27000 hits.
We won't add another one.

This computer reports 7.86 GB total RAM, 4 CPUs and 2 cores.
Beside that all LHC VMs require hardware virtualization to be enabled.
The (ATLAS) VM is configured to allocate 6.6 GB RAM and 4 processors.

The VirtualBox FAQs request to leave at least 1 core free (= not allocated for a VM).

Hence, on this computer ATLAS should be run using a 2-CPU setup.

Processor online count: 4
Processor count: 4
Processor online core count: 2
Processor core count: 2
Processor supports HW virtualization: no
Memory size: 7862 MByte
Memory available: 5177 MByte

Not sure if Windows disables HW virtualization if it doesn't have enough resources.

What's the difference

Virtualbox (5.2.44) vs. Virtualbox (6.1.32)

On the not working computer you may try Virtualbox 6.1.30 first.
If it still fails you may try Virtualbox 5.2.44

Always ensure to run all tests with fresh VMs.
Never downgrade while a VM is just suspended => they will crash and may leave garbage.

Woo Hoo. Also sorted.
Peter's fix didn't help as I have a Home edition of Windows which supposedly doesn't have Hyper-V so no amount of trying to disable it was of any benefit.
So something was still not allowing VBox to see that Virtualisation was Available and Activated.
Downgrading to VBox 6.1.30 didn't help either, nor did uninstalling a couple of Windows updates.
Further Googling found the problem reported elsewhere as well and eventually I found that an Avast Antivirus update had given it a new feature in
Menu - Settings - Troubleshooting called Enable hardware-assisted virtualisation which is checked by default but needs to be UNCHECKED
One host happy again with LHC & -dev and I'm sure the other will be, too once it finishes a couple of Rosettas and a Yoyo.

  (\_/)
 (=^.^=)
 (")_(")

You need to reboot after unchecking that box to get the setting to "stick". Hoping it fixes those machines for you, as it did mine.
I removed the Happy Bunny's "tail" typo 8¬)