Name | 07544633_081_2 |
Workunit | 5778262 |
Created | 4 Nov 2019, 20:51:37 UTC |
Sent | 4 Nov 2019, 21:21:28 UTC |
Report deadline | 9 Nov 2019, 21:21:28 UTC |
Received | 7 Nov 2019, 2:47:50 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Aborted by user |
Exit status | 203 (0x000000CB) EXIT_ABORTED_VIA_GUI |
Computer ID | 483 |
Run time | 3 min 38 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 3.32 GFLOPS |
Application version | boinc2docker v1.12 (vbox64_mt) windows_x86_64 |
Peak working set size | 10.46 MB |
Peak swap size | 6.34 MB |
Peak disk usage | 498.83 MB |
<core_client_version>7.14.2</core_client_version> <![CDATA[ <message> aborted by user</message> <stderr_txt> 2019-11-04 19:54:20 (3056): vboxwrapper (7.9.26200): starting 2019-11-04 19:54:20 (3056): Status Report: Launching vboxsvc.exe. (PID = '2848') 2019-11-04 19:56:01 (3056): Error in guest additions for VM: -182 Command: VBoxManage -q list systemproperties Output: 2019-11-04 19:56:01 (3056): Feature: Checkpoint interval offset (183 seconds) 2019-11-04 19:56:01 (3056): Detected: VirtualBox VboxManage Interface (Version: 6.0.14) 2019-11-04 19:56:01 (3056): Detected: Sandbox Configuration Enabled 2019-11-04 20:00:47 (3056): Error in host info for VM: -182 Command: VBoxManage -q list hostinfo Output: 2019-11-04 20:00:47 (3056): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory). 2019-11-04 20:00:47 (3056): WARNING: Communication with VM Hypervisor failed. 2019-11-04 20:00:47 (3056): Could not communicate with VM Hypervisor. Rescheduling execution for a later date. 2019-11-05 21:03:52 (8012): vboxwrapper (7.9.26200): starting 2019-11-05 21:03:52 (8012): Status Report: Launching vboxsvc.exe. (PID = '10784') 2019-11-05 21:05:32 (8012): Error in guest additions for VM: -182 Command: VBoxManage -q list systemproperties Output: 2019-11-05 21:05:32 (8012): Feature: Checkpoint interval offset (479 seconds) 2019-11-05 21:05:32 (8012): Detected: VirtualBox VboxManage Interface (Version: 6.0.14) 2019-11-05 21:05:32 (8012): Detected: Sandbox Configuration Enabled 2019-11-05 21:10:17 (8012): Error in host info for VM: -182 Command: VBoxManage -q list hostinfo Output: 2019-11-05 21:10:17 (8012): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory). 2019-11-05 21:10:17 (8012): WARNING: Communication with VM Hypervisor failed. 2019-11-05 21:10:17 (8012): Could not communicate with VM Hypervisor. Rescheduling execution for a later date. 2019-11-06 21:30:00 (16912): vboxwrapper (7.9.26200): starting 2019-11-06 21:30:00 (16912): Status Report: Detected vboxsvc.exe. (PID = '4032') 2019-11-06 21:30:09 (16912): Error in guest additions for VM: -2147024891 Command: VBoxManage -q list systemproperties Output: VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: The object is not ready VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient 2019-11-06 21:30:09 (16912): Feature: Checkpoint interval offset (411 seconds) 2019-11-06 21:30:09 (16912): Detected: VirtualBox VboxManage Interface (Version: 6.0.14) 2019-11-06 21:30:09 (16912): Detected: Sandbox Configuration Enabled 2019-11-06 21:33:38 (16912): Error in host info for VM: -182 Command: VBoxManage -q list hostinfo Output: 2019-11-06 21:33:38 (16912): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory). 2019-11-06 21:33:38 (16912): WARNING: Communication with VM Hypervisor failed. 2019-11-06 21:33:38 (16912): Could not communicate with VM Hypervisor. Rescheduling execution for a later date. </stderr_txt> ]]>
©2024 COPYRIGHT 2017-2018 NCN