Did you try to run cosmology at home with all 6 cores?

6. Task gets stuck with the BOINC Manager status:

Postponed: VM Hypervisor failed to enter an online state in a timely fashion.

In contrast to the well-known issue #4 on my list with the status

Postponed: VM job unmanagable, restarting later.

here it doesn't help to restart BOINC. I just had such a Task 1475946906. Now, after ~2 days, it decided to continue to process again. Let's see whether it will be finished before its deadline!

To continue the thread of issues with VritualBox tasks, the messages here identify missing CPU extensions (avx, avx2, f16c, fma) as being the culprit for issue #3 in my original post in this thread. Intel MKL crashes because one of these extensions is missing in the CPU, but presumably either VirtualBox isn't signalling that to the environment correctly, or the OS/scripts aren't picking it up properly and so try to use those missing extensions.

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=6893&postid=105762

---

To continue the thread of issues with VritualBox tasks, the messages here identify missing CPU extensions (avx, avx2, f16c, fma) as being the culprit for issue #3 in my original post in this thread.

I think it's almost certainly AVX:

We can rule out F16C becuase that was introduced in Ivy Bridge (3rd gen) Intel CPUs, whereas AVX was introduced in Sandy Bridge (2nd gen). My Sandy Bridge machine ran Virtualbox jobs quite happily, but my Nehalem machine (1st gen) doesn't.

We can rule out FMA and AVX2 as they were both introduced after F16C (both in Haswell - 4th gen).

---

Continuing my post below, the Virtualbox tasks won't run on:

Intel:
Anything older than Sandy Bridge (2nd Gen Core architecture). So Core2 CPUs and older, or original 1st gen Core CPUs (Nehalem) won't work.
Any Pentiums and Celerons older than 11th gen (Tiger Lake)

AMD:
Bulldozer and newer all support AVX, so Phenom CPUs won't work but Bulldozer, Jaguar, Puma and newer should work.[/list]

---