2 at the moment:
1
2

CPU usage is low, you can cancel. There is a problem with vbox guest additions that prevents access to work unit data and code.

CPU usage is low, you can cancel. There is a problem with vbox guest additions that prevents access to work unit data and code.

Hello,
nice advise to abort !
I have one WU running 4 days, two WU running 3 days, one running 2 days.
No any in error.
https://quchempedia.univ-angers.fr/athome/result.php?resultid=854441
https://quchempedia.univ-angers.fr/athome/result.php?resultid=853808
and so on.....
Here the four days WU : https://quchempedia.univ-angers.fr/athome/result.php?resultid=813148

I delete this project. There are much more stable as this one.

A lot of complaints and no change, exept to say the new WU will take some days.

To Admin : do you really think we will wait, days and days before to be obliged to cancel ???

---

Too many such tasks. Stopping this project.
If you wish more donors, make it stable for Windows.

Too many such tasks. Stopping this project.
If you wish more donors, make it stable for Windows.

We've tested a lot of official wrappers and it's not working. We're working on a workaround.

What's the problem with compiling a native application? Porting the program to Windows?
I am a Windows software developer, can try to help.

May it be a solution for the virtualbox app?

The Vbox job description file
...
completion_trigger_file
This provides a more bulletproof way for VM apps to exit; sometimes VMs fail to shut down, and the task hangs indefinitely. When the VM app is done, it writes a file of this name in the shared directory; the file can optionally contain an integer exit code (first line) a bool value for whether it should bubble up to the volunteer (second line) and stderr text (subsequent lines). If vboxwrapper finds this file, it cleans up the VM and exits with the given code (default 0).

https://boinc.berkeley.edu/trac/wiki/VboxApps

I notice that in the marsinph 's wrong work units that the slots used during the work unit changed.

https://quchempedia.univ-angers.fr/athome/result.php?resultid=813148
It began with slot 3 , then used slot 6 and finally unregistered slot 3.

https://quchempedia.univ-angers.fr/athome/result.php?resultid=853808
It maybe began with slot 3 , then used slot 6 and finally unregistered slot 9.

It looks as if the slot number is lost during the processing , so the savings operations are not made in the good slot.This is maybe the reason why during the computation appeared access denied.

The normal way is described as :

How it works

Using the example startup script, the steps in running a vboxwrapper app are:

    BOINC client
        Create slot directory, say slot/0
        Create slot/0/shared, and copy input files there
        Execute vboxwrapper in the slot directory 
    vboxwrapper
        Create and run virtual machine 
    Virtual machine
        Startup script
            mounts shared directory
            cd into shared directory
            execute boinc_app
            when boinc_app exits, shut down virtual machine 
    vboxwrapper
        delete virtual machine
        call boinc_finish() 
    BOINC client
        copy output files from slot/0/shared to project directory