Development for LHC@home

So, I signed up to CMS, Suspend'd & NoNewTask'd the other 40+ projects running on my biggest machine with 6 cores/12 threads and GTX 480 on Win7, added CMS to it, forced an Update, which received a single task: CMS_30012_1427806601.760414. I would have expected it to start running immediately since everything else is suspended. Nope. It is stuck at "Waiting to run". Just to test, I also Resume'd WUprop@Home, and that task immediately started running, with CMS still staying at "Waiting to run". When I Resume everything else, all other tasks start running or waiting for their turn, except for CMS.

I am running the latest BOINC (7.4.42) & VirtualBox (4.3.12), with plenty of disk & memory available. My VBox has no Machines shown in it.

I have 6 other machines, all of which also are attached to CMS, 4 of which having received a single task each, and I am pretty sure they are in the same state, but I didn't check.

Sooooo... What is going on?

Thanks
Tuna

---

Yes, the host has ATLAS and vLHC credits. Nothing changed in the BIOS. I will have to get back home to verify if another VBox app is able to run, but I am pretty sure there is no problem there. I'll doublecheck.

Nothing specific from CMS in the Event Log. I could turn on all the debug flags and do the same sequence of actions...

The host wasn't rebooted since my morning yesterday, since singing up to CMS. I'll try that, too.

One more thing I noticed: BOINC Manager thinks of the task as "Active" when I filter it to Show Active Tasks as opposed to Show All Tasks. Yet, stuck at 0%, Waiting To Run. Weird...

---

Well, I came home, suspended all projects, restarted the machine, forced the download of some jobs for ATLAS and vLHC (to test later if CMS still didn't work), turned on all the Log flags mentioned here and a few more I thought might be useful, unsuspended CMS, and it started showing progress, along with a VBox being created and getting into the running state...

So, it works. I don't know what helped it to get in gear. Reboot? Downloading ATLAS/vLHC jobs? Turning on more logging?... I have seen stranger things happen over my years.. :-)

Anyways, it works now. It is worth noting that on all my other machines that are VBox capable, CMS started its first task without the need of a reboot. So, one wonders why this one needed it.

Thanks for the help
Tuna

---