Seite 3 von 3

Re: VirtualBox v5.1.0 - PROBLEMS

Verfasst: 15.01.2017 18:53
von robertmiles
Sample of stderr.txt:

VM Exit Code: 259 (0x103)

2017-01-14 14:55:18 (9804): vboxwrapper (7.7.26197): starting
2017-01-14 14:55:18 (9804): Feature: Checkpoint interval offset (252 seconds)
2017-01-14 14:55:18 (9804): Feature: Enabling trickle-ups (Interval: 14400.000000)
2017-01-14 14:55:18 (9804): Detected: VirtualBox COM Interface (Version: 5.0.18)
2017-01-14 14:55:18 (9804): Detected: Minimum checkpoint interval (1800.000000 seconds)
2017-01-14 14:55:18 (9804): Starting VM. (boinc_ed35b4e5c438946f, slot#9)
2017-01-14 15:00:21 (9804): Successfully started VM. (PID = '9804')
2017-01-14 15:00:21 (9804): Reporting VM Process ID to BOINC.
2017-01-14 15:05:21 (9804): VM state change detected. (old = 'poweroff', new = 'aborted')
2017-01-14 15:05:26 (9804):
NOTE: VM failed to enter an online state within the timeout period.
This might be a temporary problem and so this job will be rescheduled for another time.


Hypervisor System Log:

00:10:00.356580 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
00:10:00.356580 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0


Subdirectory Logs is empty - no VBox.log file.

Re: VirtualBox v5.1.0 - PROBLEMS

Verfasst: 15.01.2017 19:40
von Jacob Klein
I am positive that VirtualBox 5.0.18 is not compatible with Windows 10 Anniversary Update Build 14393.

Since this is a v1.18 task, then if you don't have older RNA World tasks that require an old Virtualbox version, then you should install the latest VirtualBox 5.1.x version (Not 5.0.x), to see if it resolves the problem. That would be my recommendation.

Re: VirtualBox v5.1.0 - PROBLEMS

Verfasst: 16.01.2017 02:32
von robertmiles
I installed 5.1.12. After I also restarted Windows 10 and BOINC, it may have fixed the problem, but I expect it to take over 13 days to be sure.

The previous version installed was probably 5.1.4 - at least, I had downloaded that version.

I doubt if it matters, but I had to shut down BOINC use of the GPU recently.

After a Windows 10 restart and BOINC restart, one change was that all VM tasks went back to an elapsed time of zero - as expected, since none of them had written a checkpoint. The other change was that the RNA World task restarted, and has already run longer than before and has written at least one checkpoint.

Re: VirtualBox v5.1.0 - PROBLEMS

Verfasst: 16.01.2017 02:43
von Jacob Klein
Your logs showed that you had the incompatible version 5.0.18 installed. I'm glad things sound like they might be working now!

Re: VirtualBox v5.1.0 - PROBLEMS

Verfasst: 21.01.2017 01:31
von robertmiles
Now up to 21.953% progress, so it looks likely to work this time.

Re: VirtualBox v5.1.0 - PROBLEMS

Verfasst: 21.01.2017 02:36
von Jacob Klein
Expect it to go to 99.999%, then back to 98.765%, then stay there at 98.765% until complete, which could take up to 2 years :)