LHC@home

Hi,

I'm returning to LHC@Home for the first time in over 1.5 years. In my Project Preferences, I have every project set to "Yes" except for ATLAS (long sim). All 3 of the "Simulation" applications show on the Project status page available tasks now (EST 11:37am), with two of them showing thousands of available tasks. But I'm not getting anything. My Event Log shows:

11/13/2021 11:30:59 AM | LHC@home | Scheduler request completed: got 0 new tasks
11/13/2021 11:30:59 AM | LHC@home | No tasks sent
11/13/2021 11:30:59 AM | LHC@home | No tasks are available for SixTrack
11/13/2021 11:30:59 AM | LHC@home | No tasks are available for sixtracktest
11/13/2021 11:30:59 AM | LHC@home | No tasks are available for CMS Simulation
11/13/2021 11:30:59 AM | LHC@home | No tasks are available for Theory Simulation
11/13/2021 11:30:59 AM | LHC@home | No tasks are available for ATLAS Simulation

Is there something new I need to do? Am I doing something wrong? Any idea why I'm not getting any tasks?

Thanks.

Doug

You Computer information shows: "Virtualbox (6.1.12) installed, CPU does not have hardware virtualization support"
Have you enabled virtualization in the BIOS?

Also, try setting in your preferences "Max # CPUs" to 8, rather than no limit. It does not work the way it should.

Also be sure that you have ''Run native if available?'' not ticked in your project preferences.

Thanks. ''Run native if available?'' is NOT checked.

Doug

You Computer information shows: "Virtualbox (6.1.12) installed, CPU does not have hardware virtualization support"
Have you enabled virtualization in the BIOS?

I'm running Win10 with all the latest updates. In Task Manager, on the second (Performance) tab, at the bottom with all the CPU info, it says "Virtualization: Enabled". Does that address what you are asking about? I ran LHC@home fine in the past on this machine; I just haven't run it in the last 1.5 years or so.

I set my Max CPUs to 8, as you've suggested.

Thanks.

Doug

In Task Manager, on the second (Performance) tab, at the bottom with all the CPU info, it says "Virtualization: Enabled". Does that address what you are asking about?

That is probably good, but the most reliable indication that I look to is in BOINC itself.

It is best to reboot, and then look at "Tools/Event log". Somewhere around line 14 or so (in Linux for me), it will show which version of VirtualBox you are using.
If it sees that, then it should be good on any BOINC project.

It is best to reboot, and then look at "Tools/Event log". Somewhere around line 14 or so (in Linux for me), it will show which version of VirtualBox you are using.
If it sees that, then it should be good on any BOINC project.

This was in my Event Log: VirtualBox version: 6.1.12 (on line 18).

So, I guess my VB installation is not the issue. I'm still baffled why I'm not getting any tasks.

Doug

So, I guess my VB installation is not the issue. I'm still baffled why I'm not getting any tasks.

I remember back in my early days, it would ignore me for a while and then send a bunch of tasks.
I am not sure if they are past that phase or not, but just wait a while.

The Intel website shows that the CPU i5-3470 has VT-x/VT-d:
https://ark.intel.com/content/www/us/en/ark/products/68316/intel-core-i53470-processor-6m-cache-up-to-3-60-ghz.html
All options related to this in the BIOS must be enabled.


Windows may show virtualization being enabled but that's no guarantee that the BOINC client can detect it.
As long as the BOINC client reports "CPU does not have hardware virtualization support" the project will not send any VirtualBox tasks.
This issue is mostly caused by other hypervisors, e.g. Hyper-V, being active beside VirtualBox.
You will have to completely disable all of them and reboot the computer.


The reason why you don't get SixTrack is that there are not enough tasks in the server queue to satisfy all requests.

Thanks for the info.

In the BIOS on my Dell OPtiplex 7010, under "Virtualization Support", there are:
- Virtualization (enabled)
- "VT for Direct I/O" (enabled)
- Trusted Execution (NOT enabled)

In the System Information app, under System Summary, it shows:
"A hypervisor has been detected. Features required for Hyper-V will not be displayed."

I not sure if the above addresses everything you are asking about, but it's what I could find.

Doug

computezrmle wrote:

...
This issue is mostly caused by other hypervisors, e.g. Hyper-V, being active beside VirtualBox.
You will have to completely disable all of them and reboot the computer.

you wrote:

...
In the System Information app, under System Summary, it shows:
"A hypervisor has been detected. Features required for Hyper-V will not be displayed."
Doug

so from what I guess: the hypervisor may be the problem.