Hi,

Recently upgraded my PC and reinstalled Boinc and added the projects, however under host details its saying "CPU does not have hardware virtualization support"
Example https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10664526

SVM is enabled in the bios, Task manager confirms its enabled, Hyper V is also disabled as is memory integrity, so unsure why its reporting this and blocking VM jobs?

There is another thing in the bios needs to be set. I can't remember what it is without looking and am on phone at present.

Only others I can think of are IOMMU and SR IOV but neither should affect Boinc as they are for passing through PCI-E devices?

I do remember that some other projects requiring VB worked without it but not LHC. I had to check two things in bios on my Ryzen 7. The MB for my Ryzen9 clearly had the correct setup out of the box as it worked first time. Possibly amd-v? I am struggling to remember not having the machine that required it any more to check in the bios.
Edit: I also had to edit a config file using sudo changing a policy from strict. I can probably track that down in the morning.

Sorry, can't find it. I think I posted somewhere on these boards about it but my searching skills are clearly not good enough. Sadly I seem to have deleted the direct message on another forum that had not the exact answer but something close enough to let me find it.

Yea I am struggling as well, everything indicates that VT is enabled

Is resizable bar turned on or off? On some motherboards, you can only run either rebar or virtualization, not both at the same time.
Have you checked for a BIOS/UEFI update for the motherboard?

What brand and model motherboard do you have?

The board is the X870E AORUS ELITE WIFI7, Virtualisation is enabled in the bios, I have also enabled IOMMU which has made no difference.

This is a very new motherboard. Did you already try updating the BIOS?
What you can also try is resetting the BIOS to factory defaults, reboot, go back into the BIOS immediately again and set it back up.

If that doesn't fix any detection problems, and the newest BIOS update didn't either, then you have to report the behaviour to Gigabyte.

The issue is neither caused by BOINC nor by any of it's projects.
It is caused either by a BIOS setting being disabled or by a conflict between Hyper-V and VirtualBox.

The BIOS setting you need to enable is called VT-x on Intel based systems or AMD-V/SVM on AMD based systems.
Without that none of the steps below will solve the issue.

In addition you must ensure that Hyper-V does not conflict with your VirtualBox version.
Best would be to completely disable all Hyper-V/Sandbox/WSL features in Windows and run:
bcdedit /set hypervisorlaunchtype off

In addition you must disable:
Windows Security -> Device Security -> Core isolation -> Memory Integrity

and you may need to disable certain other Windows features as explained here:
https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v

Then reboot, contact a BOINC project (e.g. LHC@home) and check your computer details page there.

A wrong/incomplete configuration is reported like this and you will not get any vbox64 task:
Virtualbox (a.b.c) installed, CPU does not have hardware virtualization support

This must change to:
Virtualbox (a.b.c) installed, CPU has hardware virtualization support and it is enabled

Be aware that BIOS updates usually disable the settings mentioned above and Windows updates may reenable Hyper-V or related settings.

Hi,

Yes as above Virtualisation is enabled in the bios (latest version) Core isolation is off as is Hyper V / Sandbox and WSL.

Ill try bcdedit /set hypervisorlaunchtype off, reboot and see if that fixes it.

Edit, still no joy

Open a Powershell window, run the following command and post it's output:

Get-ComputerInfo -property "HyperV*"

HyperVisorPresent : True
HyperVRequirementDataExecutionPreventionAvailable :
HyperVRequirementSecondLevelAddressTranslation :
HyperVRequirementVirtualizationFirmwareEnabled :
HyperVRequirementVMMonitorModeExtensions :

This is what I got from an LHC@home volunteer who successfully runs VirtualBox VMs on Windows:

HyperVisorPresent : False
HyperVRequirementDataExecutionPreventionAvailable : True
HyperVRequirementSecondLevelAddressTranslation : True
HyperVRequirementVirtualizationFirmwareEnabled : True
HyperVRequirementVMMonitorModeExtensions : True

Your output suggests that you may still have left Hyper-V components active and/or SVM is not enabled in the BIOS:

HyperVisorPresent : True
HyperVRequirementVirtualizationFirmwareEnabled :

Your board (X870E AORUS ELITE WIFI7) and your CPU (AMD Ryzen 9 9950X) are known to support SVM.
The relevant BIOS entry that must be enabled is usually located here:
Advanced Frequency Settings -> Advanced CPU Settings -> SVM Mode

Don't mix this with other settings that look similar, e.g. SMT Mode.

This worked for me. Thank you!

in a clean install of 24h2 it seemed like the Memory Integrity switch didn't work so setting the regkey manually did the job.