Development for LHC@home

I've just noticed that one of my two computers hasn't gotten any work from LHCathome-dev for over a year. Granted, I set the 3 projects using VM to nowork, but that was just lately.

What would cause LHCathome-dev to send work to one of my machines, but not to the other?

Where should I start looking?

Well that pc would have to d/l the new versions (vdi and the rest) since the last ones it did run have been updated here.

But it should be able to get Theory or Atlas or LHCb here so check your Boinc manager and make sure it is set to get new work from here.

And then check your Account Preferences again and make sure that pc is set to get one of those 3 versions.

Usually Theory tasks are the easiest to get but you will still have to d/l that new version and depending on your isp they can take a while.

Main thing is looking at the Preferences (home,school,work depending on which one that pc is set as)

If all that is set right you should get work.

What does your Boinc Manager Event Log say when you try to get work??

Good luck.

---

Mad Scientist For Life

First, thanks for your help. I appreciate it.

After more digging, I have a more precise definition of the situation. Both LHC and LHC-dev are under the mistaken impression that VM isn't installed on the one machine, which is the reason neither will give up work.

6/16/2018 8:45:12 AM | LHC@home | Sending scheduler request: Requested by project.
6/16/2018 8:45:12 AM | LHC@home | Requesting new tasks for CPU
6/16/2018 8:45:16 AM | LHC@home | Scheduler request completed: got 0 new tasks
6/16/2018 8:45:16 AM | LHC@home | No tasks sent
6/16/2018 8:45:16 AM | LHC@home | Message from server: VirtualBox is not installed
6/16/2018 8:45:16 AM | LHC@home | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them

6/16/2018 8:42:22 AM | lhcathome-dev | Sending scheduler request: Requested by user.
6/16/2018 8:42:22 AM | lhcathome-dev | Requesting new tasks for CPU
6/16/2018 8:42:25 AM | lhcathome-dev | Scheduler request completed: got 0 new tasks
6/16/2018 8:42:25 AM | lhcathome-dev | No tasks sent
6/16/2018 8:42:25 AM | lhcathome-dev | Message from server: VirtualBox is not installed
6/16/2018 8:42:25 AM | lhcathome-dev | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them

Of course it is. BOINC 7.10.2 and VM 5.2.12 including the 5.2.12 expansion pack have been installed on both boxes. Cosmology@home is running quite nicely on both machines using BOINC/VM.

So the question has become why do the two LHC-related projects "see" my VM install on one machine but not the other. The installations are identical, and work well on a non-LHC-related project?

As a final point, both LHC-related projects have run successfully on both machines in the past. I stopped allowing them to run on the one machine some time ago because of problems I was having with VM locking everything up. I decided to ease back into LHC/LHC-dev just recently... a decision I'm starting to regret.

Well that is strange that the log says GPU are available here since Cern doesn't have any GPU work for any project.

As far as the VB it is something that happens if you d/l VB with the version of Boinc at the same time from the LHC sites like here or LHC

Years ago I stopped d/ling my VB version from that Boinc page.

You should try a clean install of the proper VB version from here..............https://www.virtualbox.org/wiki/Downloads

I always get the Extension Pack there too.

After the d/l and install then reboot the pc and then see if you can get a Theory task here and start it running.

That usually will fix that problem.

---

Mad Scientist For Life

Of course it is. BOINC 7.10.2 and VM 5.2.12 including the 5.2.12 expansion pack have been installed on both boxes. Cosmology@home is running quite nicely on both machines using BOINC/VM.

So the question has become why do the two LHC-related projects "see" my VM install on one machine but not the other. The installations are identical, and work well on a non-LHC-related project?

As a final point, both LHC-related projects have run successfully on both machines in the past. I stopped allowing them to run on the one machine some time ago because of problems I was having with VM locking everything up. I decided to ease back into LHC/LHC-dev just recently... a decision I'm starting to regret.

Digging into it too and guessing that the machine you mean is your Quad Q9650??

That machine did not do any work for Cosmology for at least the last 9 months.

Have a look at your client_state.xml. Is there a line <p_vm_extensions_disabled>1</p_vm_extensions_disabled> in it.
Point 5 of Yeti's checklist.