As an exercise in virtualisation I installed the SUN VirtualBox on mu SuSE Linux 11,1,. The I installed Open Solaris as a guest OS. This done I installed the BOINC client and the SETI Enhanced application by Dotsch. After a few false starts for which I apologize, having forgotten the LD_LIBRARY_PATH variable, it now runs. But my dual core Opteron 1210 which is SSE3 capable, is seen only as a pentium_pro+mmx. So it will take a long time compared to the Linux application, also enhanced.
Tullio

---

I guess that the wrong CPU capatibities are caused by the virtualisation software.
I think, that you have a overhead due running SETI in the virutal machine, which cause a slowdown. Normaly running SETI on the host system would gave better perfomance.

I have finished one unit, which was uploaded but still does not appear in the database. A second one is running but this was just an experiment. As soon as the result appears with its timing I shall kill boinc. Anyway it was an interesting exercise to install boinc and seti without a boinc manager, which I use on Linux. Cheers.
Tullio

---

One result validated with CPU time about ten times that of a Core2 Duo with Darwin 10.0.0 at 3.06 GHz while my Opteron 1210 runs at 1.8 GHz. Run time 0. Another stopped with compute error (signal 11) after 92,941.51 s of CPU time. Run time also 0. A third unit is running while the Linux host gets no unit. Wait and see.
Tullio

---

An interesting fact: while SETI is running on the virtual machine it uses 100% of one CPU core even if other BOINC programs are running. SETI and Einstein or QMC share the other core, while AQUA, which is multithreading, uses one by itself, If the virtual SETI stops because it has no work, AQUA occupies all room left by VirtualBox, which takes about 20% of CPU when idle.

---