LHC@home

This error in BOINC manager sometimes shows up.
Also, probably related since I noticed the job with that message had a collision with an undeleted previous vdi in its claimed slot, eventually hundreds of broken links to vdi files in the BOINC data\slot directories will be in the VBox media manager.

VBoxManage.exe fails to complete the deletion of the slot vdi file.

No warning or information entry is found in the Windows event logs about VBoxManage.exe or vboxwrapper_xxxxx.exe closing unexpectedly.

Raising the priority of VBoxManage.exe to normal from idle seems to have reduced the number of broken links by 90+%.

File locked error or timing out before job cleanup?

Does vboxwrapper double check that vdi remnants are cleaned up?

(Happens on all machines and they have varying versions of VBox 5.1.26, 5.1.28 and 5.2.0)

Yes Marmot, I have mentioned that several times here but with no reply so I always just check my VB Manager/File/Virtual Media Manager and *remove* them myself. (for a long time now)

Maybe with more than one person says it something will be done.

Good luck

---

Volunteer Mad Scientist For Life

...I always just check my VB Manager/File/Virtual Media Manager and *remove* them myself...

So, do you just remove/delete the vm_image.vki files that aren't attached to anything?

...I always just check my VB Manager/File/Virtual Media Manager and *remove* them myself...

So, do you just remove/delete the vm_image.vki files that aren't attached to anything?

YES.......and I check them all before I start the next batch running (I know most members don't like doing that but I like to take care of problems before they happen)

Have a HS2011-Server with CMS and Theory tasks for using.
This tasks become the work from Cern in exchange since weeks.
There are no .vdi to delete in Virtual Media manager.
So, it must be a other reason therefore.
Virtualbox for me is 5.1.30.

I first saw and reported this late May / early June. Don't know if the newer wrappers at -dev fare any better? Think it's maybe a timing issue as the wrapper exits perhaps before VBox has fully finished tidying up. I have noticed that any time VBox is stopped, eg for an update to itself or Windows, any yellow triangles get cleared, otherwise they still need to be manually deleted.

Yes Marmot, I have mentioned that several times here but with no reply so I always just check my VB Manager/File/Virtual Media Manager and *remove* them myself. (for a long time now)

When the service restarts, almost all of the broken links to vdi's get cleaned up.
So, after all VM's are stopped, try using your task/process manager and terminate the VBoxSVC.exe found under services process. Or more elegantly, use the Windows Services management console and stop and restart that service. A batch file with the appropriate net stop VBoxSVC.exe the net start can automate it. No need to restart the computer.


I think, if they would run vboxwrapper_xxxxxx at normal priority instead of idle, and when it calls vboxmanage that child process would inherit the normal priority, this issue would mostly clear up.

Since the wrapper is not using CPU slices, and it's managing the WU's in an environment where the CPU's are pegging 100% and users are trying to fit as many work units into RAM as possible, the wrapper needs to be dominant to accomplish it's management tasks.

Adjusted the vboxwrapper and vboxmanage processes to above normal priority but the dirty environment errors persist on all machines.

Maybe a bug in Oracle's VBox that LHC has no control over.