Why am i not getting WU's for my PC and VM?
The PC is running Windows and the VM LinuxMint

My CPU is a i5-4460

Why am i not getting WU's for my PC and VM?
The PC is running Windows and the VM LinuxMint

My CPU is a i5-4460

Can you post the messages from the event log when you request work? That might give us some clues. Also worth looking in the adjacent thread which may possibly be the same issue.

---

Please do not private message myself or other moderators for help. This limits the number of people who are able to help and deprives others who may benefit from the answer.

20-12-2020 18:06:24 | climateprediction.net | update requested by user
20-12-2020 18:06:26 | climateprediction.net | Sending scheduler request: Requested by user.
20-12-2020 18:06:26 | climateprediction.net | Requesting new tasks for CPU
20-12-2020 18:06:28 | climateprediction.net | Scheduler request completed: got 0 new tasks
20-12-2020 18:06:28 | climateprediction.net | No tasks sent
20-12-2020 18:06:28 | climateprediction.net | Project requested delay of 3636 seconds
20-12-2020 18:12:08 | climateprediction.net | update requested by user
20-12-2020 18:12:08 | climateprediction.net | Sending scheduler request: Requested by user.
20-12-2020 18:12:08 | climateprediction.net | Requesting new tasks for CPU
20-12-2020 18:12:10 | climateprediction.net | Scheduler request completed: got 0 new tasks
20-12-2020 18:12:10 | climateprediction.net | Not sending work - last request too recent: 342 sec
20-12-2020 18:12:10 | climateprediction.net | Project requested delay of 3636 seconds

That seems to be an increasingly common problem, of no work sent, and no reason why.
It's currently being investigated

The first post about it is here, under New work Discussion.
The problem is now being talked about on the BOINC site.

20-12-2020 18:06:28 | climateprediction.net | Project requested delay of 3636 seconds
20-12-2020 18:12:08 | climateprediction.net | update requested by user
20-12-2020 18:12:08 | climateprediction.net | Sending scheduler request: Requested by user.
20-12-2020 18:12:08 | climateprediction.net | Requesting new tasks for CPU
20-12-2020 18:12:10 | climateprediction.net | Scheduler request completed: got 0 new tasks
20-12-2020 18:12:10 | climateprediction.net | Not sending work - last request too recent: 342 sec
20-12-2020 18:12:10 | climateprediction.net | Project requested delay of 3636 seconds

In the last series of lines from your log, the project says it requested a delay of an hour for communications from your computer. When you forced a communication with the project, it came back and said the communication was to soon and wouldn't send any tasks because of that, then the project requested another delay in comms for another hour. Unfortunately, once a communication occurs between your computer and the project, you cannot force another one successfully requesting work before that hour is up. And if you do, it will delay that possibility another hour.

That is not the problem with the first communication in your log listing though. As Les said, we've been hearing of more of these problems lately.

If you are running multiple projects, you may have success if you suspend the other projects temporarily, then let boinc request work from cpdn. If you force a request, make sure it was at least an hour after the last comms between your computer and cpdn.

Thanks Geophi, I will try that tomorrow

Still doesn't work :(

Does CPDN check the amount of memory a computer (or VM) has before sending a task? Or any other characteristic such as CPU capability or disk space?

I notice that daanbusman has less than 2 GB of memory on his Linux "machines". Might he not meet some minimum requirement?

---

Oh good grief, yes. How many times do we have to tell people?
You need LOTS of memory for these models.

At least 4 gigs per model, otherwise you're just wasting everyone's time.

Does CPDN check the amount of memory a computer (or VM) has before sending a task? Or any other characteristic such as CPU capability or disk space?

I notice that daanbusman has less than 2 GB of memory on his Linux "machines". Might he not meet some minimum requirement?

Not sure. The task's rsc_memory_bound in client_state.xml for the hadam4h N216 models is about 364 MB (not a good actual estimate for the tasks requirements, but shouldn't be the cause of the download problem), and the actual max memory taken up by these tasks is about 1.4 GB. In theory, if the rsc_memory_bound is greater than the available RAM in the host, the server won't send a task to that PC. That wouldn't appear to be the case with his Linux VM. What I would expect to happen if he downloaded one is that it would be on the fine edge of having enough memory given how much the OS takes. He would be better off allocating at least 3 GB to that Linux VM if only running 1 task and not really doing anything else on that VM.

daanbusman -- If you allocate at least 3 GB memory to that Linux VM with 1 CPU core allocated, that should work fine for the hadam4h, if you are able to download a task. Also, you should make sure you run benchmarks in boinc because they are showing up as 1 billion ops/sec for both floating point and integer and that's not right for that CPU. If you are able to download a task, more realistic benchmark values will give your more realistic estimates for time to task completion.

You should do the things I suggest no matter what if you are able to download a task or not, but I'm far from certain that those changes will allow you to get a task. Sorry I couldn't be more helpful.

My GPU is not recognised by Linux Mint

I have updated the kernel etc and i am running Virtualbox

My GPU is not recognised by Linux Mint

I have updated the kernel etc and i am running Virtualbox

GPU isn't used by CPDN. To get BOINC working with GPU on my Xubuntu box I had to install the proprietary drivers.

---

Please do not private message myself or other moderators for help. This limits the number of people who are able to help and deprives others who may benefit from the answer.

My GPU is not recognised by Linux Mint

I have updated the kernel etc and i am running Virtualbox

GPU isn't used by CPDN. To get BOINC working with GPU on my Xubuntu box I had to install the proprietary drivers.

What Dave said is true about GPU and cpdn is true. Further, in a VM using typical VM software and typical hardware, you don't get true hardware video acceleration and can't really install the proprietary drivers.