LHC@home

hi,

For a while now, since I've updated my bios, the server has registered my host as : " Virtualbox (6.1.16) installed, CPU does not have hardware virtualization support"

the problem is that virtualbox is running with whonix which as you surely know is a debian 64 bits. So if it wasn't activated, I wouldn't be able to run whonix.
So is it a problem with virtualbox itself? or is boinc not detecting correctly the virt upport?

---

and I just noticed but it didn't detected correctly the RAM amount on the GPU which should be 8GB not 4GB

---

and also the virtuliazation is noted as supported in the task maanger

---

It's not clear why you mention whonix which is a Linux OS.
Your BOINC client identifies Windows 10:
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10670359

The GFLOPS values on that page are far too low for that CPU.

What OS do you really run on that computer?

It's not clear why you mention whonix which is a Linux OS.
Your BOINC client identifies Windows 10:
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10670359

The GFLOPS values on that page are far too low for that CPU.

What OS do you really run on that computer?

Yeah well apparently we didn't understand each other:
When I write -> I'm running virtualbox with whonix
That does mean that I'm able to run whonix inside virtualbox. Especially if I've specified that it is a 64bit debian.Which meant that I've insisted that it is a 64 bits OS which means that if the virtualization support extension weren't available, it could not be launched. That's what I meant. I thought it was clear enough but apparently not.

So obviously windows 10 pro is running.2004 if I need to specify the version.

---

maybe it's boinc issue so that's why also I'm asking here, to know if I need to redirect my statement to boinc community boards or not;

---

Your computer details page still states the CPU has no virtualization.
Since it is a Ryzen 7 this is either a wrong BIOS setting or you are running other hypervisors.

See Yeti's checklist for details and help and also this Microsoft post:
https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v

Your computer details page still states the CPU has no virtualization.
Since it is a Ryzen 7 this is either a wrong BIOS setting or you are running other hypervisors.

See Yeti's checklist for details and help and also this Microsoft post:
https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v

I'm sorry but I just looked in the bios and everything is activated plus as I said the task manager stated the thing as activated so.... no msitakes there.
If there were any other hypervisors then I wouldn't be able to launch a 64 bits OS in virtualbox as we speak. Don't you think? At least it's my experience. There would be a beautiful error message tell me that virtualbox can't get access to the ressources.

So I'm sorry to ask you again but who is responsible for the problems in boinc? In this specific case. Boinc itself or your server?

Do you use Hyper-V or Docker ? They will interfere with VirtualBox and cause problems. You should deactivate, better uninstall them

this point seems overthetop to include docker. Docker can run in WSL. And there is no actual reason that it would interfere then with an hypervisor if installed in WSL2 activated. I have it and unless there is some kind of bad code in boinc (which should be resolved immediatley quite frankly), there is no interference with it with any hypervisors I have tried over the years with any guest OS.

Check, if you have have enough RAM for Atlas available. Each SingeCore-Atlas-Task needs 2,1 GB free RAM, MultiCore-WUs need 3,0 GB + 0,9 GB * number of cores (Last Update from 01.08.2018) So 7,5 GB for a 5-Core WU.

if the RAM is filled could that be a cause for the server to say the vm extensions is not activated?


hyper-V was not activated as I've stated before.
the cpuinfo leomoon clearly detect the SVM
the systinternal coreinfo tool doesn't detect it.

---

also leomoon cpuinfo doesn't seem very reliable because I've run it on other hosts and it doesn't detect vt-x on intel cpu like an i7-7700k, i7-8700k or others where hyper-V is enabled and launched with virtual machine running. If it wasn't enabled, then running virtual machine would not be possible.
Just my 2 cents

---

also leomoon cpuinfo doesn't seem very reliable because I've run it on other hosts and it doesn't detect vt-x on intel cpu like an i7-7700k, i7-8700k or others where hyper-V is enabled and launched with virtual machine running. If it wasn't enabled, then running virtual machine would not be possible.
Just my 2 cents

same thing for coreinfo from sysinternals.

---

according to that link, it seems normal
https://serverfault.com/questions/437660/coreinfo-reports-i7-3770-cpu-doesnt-support-ept-aka-slat-and-vmx

---

the only thing that is installed is virtual machine platform but that's normal for WSL2 and the rest as indicated there :https://www.configserverfirewall.com/windows-10/please-enable-the-virtual-machine-platform-windows-feature-and-ensure-virtualization-is-enabled-in-the-bios/

So what should I do? Why your server is recognizing it as no VM support while it is obviously running VMs. Is it a problem with virtualbox and should I resintall it?

---

SVM is the Parameter in the BIOS to enable HardwareAcceleration for a Ryzen PC.

There are hundreds of posts across the internet stating there are still lots of Problems if you try to run VirtualBox beside another hypervisor. Even posts related to Microsoft.

Just a few examples regarding WSL2 which you mentioned in your last post:
https://stackoverflow.com/questions/62184881/virtualbox-and-wsl2
https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware-or-virtualbox
https://github.com/MicrosoftDocs/WSL/issues?q=is%3Aissue+virtualbox+sort%3Acomments-desc


The primary advice if you want to run LHC vbox tasks is to deactivate/deinstall all other hypervisors.
Other combinations require to be tested on your system.
They might work or not, often at the expense of very poor performance.

mmmh okey, it's just strange because it was working before. That's why I'm a little surprise but I guess the problem has been the change to 1809 to 2004.
Of course between my need of docker for development in windows and the ressources I might hand over to the project, well I need to get my priorities straight.

Thanks for your help anyway.
I might also add that in any case, there is still a bug in boinc about WSL since on all of my host WSL is not recognized by boinc, so it's not like boinc is exempt of bugs.

---

SVM is the Parameter in the BIOS to enable HardwareAcceleration for a Ryzen PC.

as stated before it was already activated and working as expected. but thanks

---