Both single and multi-core jobs run from a single slot. One slot per job, doesn't matter how much resources the job uses.

---

So he runs two or more 'tasks' at the same time. One task per VM, one VM per slot.

---

I have emailed one of the developers, but due to time differences and him working elsewhere than on BOINC these days, it can take hours or days for him to answer.

---

All right, according to the BOINC developers, this is an artifact of VMs failing.
It's not a bug, and doesn't mean that a task actually uses 2 slots.

---

Both single and multi-core jobs run from a single slot. One slot per job, doesn't matter how much resources the job uses.

So does that mean that when task x is suspended in favor of a higher priority task, task x has to wait until its original slot is available again in order to be resumed?

So does that mean that when task x is suspended in favor of a higher priority task, task x has to wait until its original slot is available again in order to be resumed?

A task stays in its slot until it has met a boinc_finish() and is unloaded.

It's not that when a task suspends that it releases the slot it's in, because we only have 4 or 8 slots. There's no real limit to slot directories that can be made and used/be in use. So tasks stay in their own slot from their start to their finish, no matter how many times you suspend them in between.

---

It's not that when a task suspends that it releases the slot it's in, because we only have 4 or 8 slots. There's no real limit to slot directories that can be made and used/be in use. So tasks stay in their own slot from their start to their finish, no matter how many times you suspend them in between.

Thanks for the enlightenment!