Task 7347015

Name	07555936_13_3
Workunit	6005157
Created	4 Nov 2019, 21:02:33 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	1 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.48 MB
Peak swap size	6.34 MB
Peak disk usage	941.55 MB
Stderr output

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
aborted by user</message>
<stderr_txt>
2019-11-04 19:22:23 (11356): vboxwrapper (7.9.26200): starting
2019-11-04 19:22:23 (11356): Status Report: Launching vboxsvc.exe. (PID = '8168')
2019-11-04 19:24:04 (11356): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:

2019-11-04 19:24:04 (11356): Feature: Checkpoint interval offset (79 seconds)
2019-11-04 19:24:04 (11356): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-04 19:24:04 (11356): Detected: Sandbox Configuration Enabled
2019-11-04 19:28:56 (11356): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo 
Output:

2019-11-04 19:28:56 (11356): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-04 19:28:56 (11356): WARNING: Communication with VM Hypervisor failed.
2019-11-04 19:28:56 (11356): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-04 19:47:31 (4164): vboxwrapper (7.9.26200): starting
2019-11-04 19:47:31 (4164): Status Report: Launching vboxsvc.exe. (PID = '4004')
2019-11-04 19:47:45 (4164): 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-04 19:47:45 (4164): Feature: Checkpoint interval offset (249 seconds)
2019-11-04 19:47:45 (4164): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-04 19:47:45 (4164): Detected: Sandbox Configuration Enabled
2019-11-04 19:50:12 (4164): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo 
Output:

2019-11-04 19:50:12 (4164): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-04 19:50:12 (4164): WARNING: Communication with VM Hypervisor failed.
2019-11-04 19:50:12 (4164): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-05 20:51:00 (5228): vboxwrapper (7.9.26200): starting
2019-11-05 20:51:00 (5228): Status Report: Launching vboxsvc.exe. (PID = '11992')
2019-11-05 20:52:40 (5228): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:

2019-11-05 20:52:40 (5228): Feature: Checkpoint interval offset (313 seconds)
2019-11-05 20:52:40 (5228): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-05 20:52:40 (5228): Detected: Sandbox Configuration Enabled
2019-11-05 20:57:25 (5228): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo 
Output:

2019-11-05 20:57:25 (5228): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-05 20:57:25 (5228): WARNING: Communication with VM Hypervisor failed.
2019-11-05 20:57:25 (5228): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-06 21:12:17 (4256): vboxwrapper (7.9.26200): starting
2019-11-06 21:12:17 (4256): Status Report: Launching vboxsvc.exe. (PID = '14948')
2019-11-06 21:13:57 (4256): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:

2019-11-06 21:13:57 (4256): Feature: Checkpoint interval offset (255 seconds)
2019-11-06 21:13:57 (4256): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-06 21:13:57 (4256): Detected: Sandbox Configuration Enabled
2019-11-06 21:18:55 (4256): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo 
Output:

2019-11-06 21:18:55 (4256): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-06 21:18:55 (4256): WARNING: Communication with VM Hypervisor failed.
2019-11-06 21:18:55 (4256): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-06 21:29:59 (8696): vboxwrapper (7.9.26200): starting
2019-11-06 21:29:59 (8696): Status Report: Launching vboxsvc.exe. (PID = '16828')
2019-11-06 21:30:09 (8696): 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 (8696): Feature: Checkpoint interval offset (520 seconds)
2019-11-06 21:30:09 (8696): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-06 21:30:09 (8696): Detected: Sandbox Configuration Enabled
2019-11-06 21:32:51 (8696): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo 
Output:

2019-11-06 21:32:51 (8696): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-06 21:32:51 (8696): WARNING: Communication with VM Hypervisor failed.
2019-11-06 21:32:51 (8696): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.

</stderr_txt>
]]>