Development for LHC@home

One of my tasks has gotten screwed up somehow. Here is the data from the VB Manager screen:

Runtime error opening 'C:\ProgramData\BOINC\slots\1\boinc_a4ae6e89571c0a8a\boinc_a4ae6e89571c0a8a.vbox' for reading: -103(Path not found.).

F:\tinderbox\win-5.0\src\VBox\Main\src-server\MachineImpl.cpp[740] (long __cdecl Machine::i_registeredInit(void)).
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Not sure exactly what all this means, but the (Path not found) part doesn't sound good.

One of my tasks has gotten screwed up somehow. Here is the data from the VB Manager screen:

Runtime error opening 'C:\ProgramData\BOINC\slots\1\boinc_a4ae6e89571c0a8a\boinc_a4ae6e89571c0a8a.vbox' for reading: -103(Path not found.).

F:\tinderbox\win-5.0\src\VBox\Main\src-server\MachineImpl.cpp[740] (long __cdecl Machine::i_registeredInit(void)).
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Not sure exactly what all this means, but the (Path not found) part doesn't sound good.

My first guess would be that you interrupted a task for too long -- how long "too long" is these days I'm not sure, I haven't been following that line of investigation closely. Does the file exist? If not, then BOINC must have thought the task finished and closed the slot. Suggest you abort the task and see if the new one starts up OK.

---

Suggest you abort the task and see if the new one starts up OK.

Actually, that was my first of many guesses, but I don't have any such task. I have 3 vLHC tasks assigned - one from -dev and two from vLHC. All three tasks are actually running (according to BOINC). The VB Manager shows all three VM as being powered off but I've asked about that already. Apparently it doesn't matter.

Bottom line - I no longer have any such task; just the abandoned VM and it's apparently broken.

I'm going to raise an issue here in general terms since it may simply be my imagination, and if not, may not even apply to vLHC. After I got VB correctly installed and functional and was processing LHC stuff, I also started getting VB stuff from cosmology@home, which is okay - I wanted to. However, I'm starting to get the feeling that the two - LHC and Cosmology - are not playing well together. Nothing concrete - yet. Just a feeling.

Never mind, Ivan. I got it figured out. The task belonged to Cosmology@home. The stack dump indicated that the VM machine was deregistered, but it wasn't. I'll toss it over their fence and see what happened.

Thanks for your help.