Task 7393251
| Name | 07560052_16_0 |
| Workunit | 6055496 |
| Created | 6 Nov 2019, 13:25:26 UTC |
| Sent | 6 Nov 2019, 14:02:11 UTC |
| Report deadline | 11 Nov 2019, 14:02:11 UTC |
| Received | 25 Nov 2019, 11:38:24 UTC |
| Server state | Over |
| Outcome | Success |
| Client state | Done |
| Exit status | 0 (0x00000000) |
| Computer ID | 3324 |
| Run time | 4 min 27 sec |
| CPU time | 3 min 10 sec |
| Validate state | Task was reported too late to validate |
| Credit | 0.00 |
| Device peak FLOPS | 3.82 GFLOPS |
| Application version | boinc2docker v1.12 (vbox64_mt) windows_x86_64 |
| Peak working set size | 155.44 MB |
| Peak swap size | 182.86 MB |
| Peak disk usage | 600.63 MB |
Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<stderr_txt>
2019-11-06 16:27:13 (7224): vboxwrapper (7.9.26200): starting
2019-11-06 16:27:13 (7224): Status Report: Launching vboxsvc.exe. (PID = '3364')
2019-11-06 16:28:06 (7224): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-06 16:28:06 (7224): Feature: Checkpoint interval offset (432 seconds)
2019-11-06 16:28:06 (7224): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-06 16:28:06 (7224): Detected: Sandbox Configuration Enabled
2019-11-06 16:32:52 (7224): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-06 16:32:52 (7224): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-06 16:32:52 (7224): WARNING: Communication with VM Hypervisor failed.
2019-11-06 16:32:52 (7224): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-07 11:19:01 (1908): vboxwrapper (7.9.26200): starting
2019-11-07 11:19:01 (1908): Status Report: Launching vboxsvc.exe. (PID = '2216')
2019-11-07 11:20:46 (1908): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-07 11:20:46 (1908): Feature: Checkpoint interval offset (114 seconds)
2019-11-07 11:20:46 (1908): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-07 11:20:46 (1908): Detected: Sandbox Configuration Enabled
2019-11-07 11:25:45 (1908): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-07 11:25:45 (1908): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-07 11:25:45 (1908): WARNING: Communication with VM Hypervisor failed.
2019-11-07 11:25:45 (1908): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-08 16:07:43 (664): vboxwrapper (7.9.26200): starting
2019-11-08 16:07:44 (664): Status Report: Launching vboxsvc.exe. (PID = '8988')
2019-11-08 16:09:26 (664): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-08 16:09:26 (664): Feature: Checkpoint interval offset (40 seconds)
2019-11-08 16:09:26 (664): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-08 16:09:26 (664): Detected: Sandbox Configuration Enabled
2019-11-08 16:14:12 (664): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-08 16:14:12 (664): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-08 16:14:12 (664): WARNING: Communication with VM Hypervisor failed.
2019-11-08 16:14:12 (664): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-09 16:16:45 (10412): vboxwrapper (7.9.26200): starting
2019-11-09 16:16:45 (10412): Status Report: Launching vboxsvc.exe. (PID = '10284')
2019-11-09 16:18:29 (10412): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-09 16:18:29 (10412): Feature: Checkpoint interval offset (23 seconds)
2019-11-09 16:18:29 (10412): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-09 16:18:29 (10412): Detected: Sandbox Configuration Enabled
2019-11-09 16:23:28 (10412): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-09 16:23:28 (10412): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-09 16:23:28 (10412): WARNING: Communication with VM Hypervisor failed.
2019-11-09 16:23:28 (10412): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-10 16:23:38 (2044): vboxwrapper (7.9.26200): starting
2019-11-10 16:23:38 (2044): Status Report: Launching vboxsvc.exe. (PID = '6408')
2019-11-10 16:25:23 (2044): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-10 16:25:23 (2044): Feature: Checkpoint interval offset (122 seconds)
2019-11-10 16:25:23 (2044): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-10 16:25:23 (2044): Detected: Sandbox Configuration Enabled
2019-11-10 16:30:22 (2044): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-10 16:30:22 (2044): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-10 16:30:22 (2044): WARNING: Communication with VM Hypervisor failed.
2019-11-10 16:30:22 (2044): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-11 16:30:47 (5216): vboxwrapper (7.9.26200): starting
2019-11-11 16:30:47 (5216): Status Report: Launching vboxsvc.exe. (PID = '9520')
2019-11-11 16:32:32 (5216): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-11 16:32:32 (5216): Feature: Checkpoint interval offset (312 seconds)
2019-11-11 16:32:32 (5216): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-11 16:32:32 (5216): Detected: Sandbox Configuration Enabled
2019-11-11 16:37:31 (5216): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-11 16:37:31 (5216): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-11 16:37:31 (5216): WARNING: Communication with VM Hypervisor failed.
2019-11-11 16:37:31 (5216): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-12 16:37:34 (5528): vboxwrapper (7.9.26200): starting
2019-11-12 16:37:34 (5528): Status Report: Launching vboxsvc.exe. (PID = '9640')
2019-11-12 16:39:18 (5528): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-12 16:39:18 (5528): Feature: Checkpoint interval offset (331 seconds)
2019-11-12 16:39:18 (5528): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-12 16:39:18 (5528): Detected: Sandbox Configuration Enabled
2019-11-12 16:44:17 (5528): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-12 16:44:17 (5528): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-12 16:44:17 (5528): WARNING: Communication with VM Hypervisor failed.
2019-11-12 16:44:17 (5528): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-13 16:44:58 (12084): vboxwrapper (7.9.26200): starting
2019-11-13 16:44:58 (12084): Status Report: Launching vboxsvc.exe. (PID = '12556')
2019-11-13 16:46:54 (12084): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-13 16:46:54 (12084): Feature: Checkpoint interval offset (123 seconds)
2019-11-13 16:46:54 (12084): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-13 16:46:54 (12084): Detected: Sandbox Configuration Enabled
2019-11-13 16:52:26 (12084): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-13 16:52:26 (12084): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-13 16:52:26 (12084): WARNING: Communication with VM Hypervisor failed.
2019-11-13 16:52:26 (12084): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-14 00:41:59 (4964): vboxwrapper (7.9.26200): starting
2019-11-14 00:41:59 (4964): Status Report: Launching vboxsvc.exe. (PID = '5116')
2019-11-14 00:43:57 (4964): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-14 00:43:57 (4964): Feature: Checkpoint interval offset (297 seconds)
2019-11-14 00:43:57 (4964): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-14 00:43:57 (4964): Detected: Sandbox Configuration Enabled
2019-11-14 00:49:26 (4964): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-14 00:49:26 (4964): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-14 00:49:26 (4964): WARNING: Communication with VM Hypervisor failed.
2019-11-14 00:49:26 (4964): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-15 00:49:30 (6436): vboxwrapper (7.9.26200): starting
2019-11-15 00:49:30 (6436): Status Report: Launching vboxsvc.exe. (PID = '3888')
2019-11-15 00:51:24 (6436): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-15 00:51:24 (6436): Feature: Checkpoint interval offset (385 seconds)
2019-11-15 00:51:24 (6436): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-15 00:51:24 (6436): Detected: Sandbox Configuration Enabled
2019-11-15 00:56:50 (6436): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-15 00:56:50 (6436): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-15 00:56:50 (6436): WARNING: Communication with VM Hypervisor failed.
2019-11-15 00:56:50 (6436): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-16 00:56:55 (7836): vboxwrapper (7.9.26200): starting
2019-11-16 00:56:55 (7836): Status Report: Launching vboxsvc.exe. (PID = '5588')
2019-11-16 00:58:48 (7836): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-16 00:58:48 (7836): Feature: Checkpoint interval offset (469 seconds)
2019-11-16 00:58:48 (7836): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-16 00:58:48 (7836): Detected: Sandbox Configuration Enabled
2019-11-16 01:04:12 (7836): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-16 01:04:12 (7836): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-16 01:04:12 (7836): WARNING: Communication with VM Hypervisor failed.
2019-11-16 01:04:12 (7836): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-17 01:04:34 (1892): vboxwrapper (7.9.26200): starting
2019-11-17 01:04:34 (1892): Status Report: Launching vboxsvc.exe. (PID = '8288')
2019-11-17 01:06:20 (1892): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-17 01:06:20 (1892): Feature: Checkpoint interval offset (113 seconds)
2019-11-17 01:06:20 (1892): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-17 01:06:20 (1892): Detected: Sandbox Configuration Enabled
2019-11-17 01:11:45 (1892): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-17 01:11:45 (1892): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-17 01:11:45 (1892): WARNING: Communication with VM Hypervisor failed.
2019-11-17 01:11:45 (1892): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-18 01:11:53 (10136): vboxwrapper (7.9.26200): starting
2019-11-18 01:11:53 (10136): Status Report: Launching vboxsvc.exe. (PID = '1464')
2019-11-18 01:13:38 (10136): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-18 01:13:38 (10136): Feature: Checkpoint interval offset (6 seconds)
2019-11-18 01:13:38 (10136): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-18 01:13:38 (10136): Detected: Sandbox Configuration Enabled
2019-11-18 01:18:37 (10136): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-18 01:18:37 (10136): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-18 01:18:37 (10136): WARNING: Communication with VM Hypervisor failed.
2019-11-18 01:18:37 (10136): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-18 07:38:07 (5248): vboxwrapper (7.9.26200): starting
2019-11-18 07:38:07 (5248): Status Report: Launching vboxsvc.exe. (PID = '5676')
2019-11-18 07:38:43 (5204): vboxwrapper (7.9.26200): starting
2019-11-18 07:38:43 (5204): Status Report: Launching vboxsvc.exe. (PID = '6084')
2019-11-18 07:40:29 (5204): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-18 07:40:29 (5204): Feature: Checkpoint interval offset (311 seconds)
2019-11-18 07:40:29 (5204): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-18 07:40:29 (5204): Detected: Sandbox Configuration Enabled
2019-11-18 07:45:24 (5204): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-18 07:45:24 (5204): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-18 07:45:24 (5204): WARNING: Communication with VM Hypervisor failed.
2019-11-18 07:45:24 (5204): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-19 07:46:19 (5016): vboxwrapper (7.9.26200): starting
2019-11-19 07:46:19 (5016): Status Report: Launching vboxsvc.exe. (PID = '8636')
2019-11-19 07:48:03 (5016): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-19 07:48:03 (5016): Feature: Checkpoint interval offset (300 seconds)
2019-11-19 07:48:03 (5016): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-19 07:48:03 (5016): Detected: Sandbox Configuration Enabled
2019-11-19 07:53:01 (5016): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-19 07:53:01 (5016): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-19 07:53:01 (5016): WARNING: Communication with VM Hypervisor failed.
2019-11-19 07:53:01 (5016): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-20 07:53:12 (13164): vboxwrapper (7.9.26200): starting
2019-11-20 07:53:12 (13164): Status Report: Launching vboxsvc.exe. (PID = '4400')
2019-11-20 07:54:56 (13164): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-20 07:54:56 (13164): Feature: Checkpoint interval offset (187 seconds)
2019-11-20 07:54:56 (13164): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-20 07:54:56 (13164): Detected: Sandbox Configuration Enabled
2019-11-20 07:59:56 (13164): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-20 07:59:56 (13164): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-20 07:59:56 (13164): WARNING: Communication with VM Hypervisor failed.
2019-11-20 07:59:56 (13164): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-21 08:00:18 (6112): vboxwrapper (7.9.26200): starting
2019-11-21 08:00:18 (6112): Status Report: Launching vboxsvc.exe. (PID = '16456')
2019-11-21 08:02:03 (6112): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-21 08:02:03 (6112): Feature: Checkpoint interval offset (366 seconds)
2019-11-21 08:02:03 (6112): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-21 08:02:03 (6112): Detected: Sandbox Configuration Enabled
2019-11-21 08:07:02 (6112): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-21 08:07:02 (6112): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-21 08:07:02 (6112): WARNING: Communication with VM Hypervisor failed.
2019-11-21 08:07:02 (6112): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-22 08:07:18 (13476): vboxwrapper (7.9.26200): starting
2019-11-22 08:07:18 (13476): Status Report: Launching vboxsvc.exe. (PID = '7324')
2019-11-22 08:09:03 (13476): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-22 08:09:03 (13476): Feature: Checkpoint interval offset (206 seconds)
2019-11-22 08:09:03 (13476): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-22 08:09:03 (13476): Detected: Sandbox Configuration Enabled
2019-11-22 08:13:54 (13476): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-22 08:13:54 (13476): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-22 08:13:54 (13476): WARNING: Communication with VM Hypervisor failed.
2019-11-22 08:13:54 (13476): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-23 08:14:26 (11864): vboxwrapper (7.9.26200): starting
2019-11-23 08:14:26 (11864): Status Report: Launching vboxsvc.exe. (PID = '21756')
2019-11-23 08:16:10 (11864): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-23 08:16:10 (11864): Feature: Checkpoint interval offset (110 seconds)
2019-11-23 08:16:10 (11864): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-23 08:16:10 (11864): Detected: Sandbox Configuration Enabled
2019-11-23 08:21:09 (11864): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-23 08:21:09 (11864): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-23 08:21:09 (11864): WARNING: Communication with VM Hypervisor failed.
2019-11-23 08:21:09 (11864): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-24 08:21:19 (9756): vboxwrapper (7.9.26200): starting
2019-11-24 08:21:19 (9756): Status Report: Launching vboxsvc.exe. (PID = '6348')
2019-11-24 08:23:04 (9756): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-24 08:23:04 (9756): Feature: Checkpoint interval offset (584 seconds)
2019-11-24 08:23:04 (9756): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-24 08:23:04 (9756): Detected: Sandbox Configuration Enabled
2019-11-24 08:28:03 (9756): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-24 08:28:03 (9756): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-24 08:28:03 (9756): WARNING: Communication with VM Hypervisor failed.
2019-11-24 08:28:03 (9756): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-25 08:28:42 (13076): vboxwrapper (7.9.26200): starting
2019-11-25 08:28:42 (13076): Status Report: Launching vboxsvc.exe. (PID = '12140')
2019-11-25 08:30:25 (13076): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-25 08:30:25 (13076): Feature: Checkpoint interval offset (182 seconds)
2019-11-25 08:30:25 (13076): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-25 08:30:25 (13076): Detected: Sandbox Configuration Enabled
2019-11-25 08:35:24 (13076): Error in host info for VM: -182
Command:
VBoxManage -q list hostinfo
Output:
2019-11-25 08:35:24 (13076): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2019-11-25 08:35:24 (13076): WARNING: Communication with VM Hypervisor failed.
2019-11-25 08:35:24 (13076): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-25 10:52:27 (5900): vboxwrapper (7.9.26200): starting
2019-11-25 10:52:27 (5900): Status Report: Launching vboxsvc.exe. (PID = '5260')
2019-11-25 10:52:28 (5900): Feature: Checkpoint interval offset (353 seconds)
2019-11-25 10:52:28 (5900): Detected: VirtualBox COM Interface (Version: 5.0.40)
2019-11-25 10:52:28 (5900): Detected: Sandbox Configuration Enabled
2019-11-25 10:52:28 (5900): Detected: Minimum checkpoint interval (600.000000 seconds)
2019-11-25 10:52:28 (5900): Create VM. (boinc_a319cc6e207193ae, slot#8)
2019-11-25 10:52:28 (5900): Updating drive controller type and model for desired configuration.
2019-11-25 10:52:28 (5900): Setting Memory Size for VM. (3072MB)
2019-11-25 10:52:28 (5900): Setting CPU Count for VM. (1)
2019-11-25 10:52:28 (5900): Setting Chipset Options for VM.
2019-11-25 10:52:28 (5900): Setting Boot Options for VM.
2019-11-25 10:52:28 (5900): Enabling VM Network Access.
2019-11-25 10:52:28 (5900): Setting Network Configuration for NAT.
2019-11-25 10:52:28 (5900): Disabling USB Support for VM.
2019-11-25 10:52:28 (5900): Disabling COM Port Support for VM.
2019-11-25 10:52:28 (5900): Disabling LPT Port Support for VM.
2019-11-25 10:52:28 (5900): Disabling Audio Support for VM.
2019-11-25 10:52:28 (5900): Disabling Clipboard Support for VM.
2019-11-25 10:52:28 (5900): Disabling Drag and Drop Support for VM.
2019-11-25 10:52:28 (5900): Adding storage controller(s) to VM.
2019-11-25 10:52:28 (5900): Adding virtual ISO 9660 disk drive to VM. (vm_isocontext.iso)
2019-11-25 10:52:28 (5900): Adding VirtualBox Guest Additions to VM.
2019-11-25 10:52:28 (5900): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB)
2019-11-25 10:52:28 (5900): Enabling shared directory for VM.
2019-11-25 10:52:28 (5900): Starting VM. (boinc_a319cc6e207193ae, slot#8)
2019-11-25 11:00:40 (9844): vboxwrapper (7.9.26200): starting
2019-11-25 11:00:40 (9844): Status Report: Launching vboxsvc.exe. (PID = '6732')
2019-11-25 11:00:40 (9844): Feature: Checkpoint interval offset (589 seconds)
2019-11-25 11:00:40 (9844): Detected: VirtualBox COM Interface (Version: 5.0.40)
2019-11-25 11:00:40 (9844): Detected: Sandbox Configuration Enabled
2019-11-25 11:00:40 (9844): Detected: Minimum checkpoint interval (600.000000 seconds)
2019-11-25 11:00:40 (9844): Starting VM. (boinc_a319cc6e207193ae, slot#8)
2019-11-25 11:05:42 (9844): Successfully started VM. (PID = '9844')
2019-11-25 11:05:42 (9844): Reporting VM Process ID to BOINC.
2019-11-25 11:10:42 (9844): VM is no longer is a running state. It is in 'poweroff'.
2019-11-25 11:10:47 (9844):
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:
VirtualBox COM Server 5.0.40 r115130 win.amd64 (Apr 28 2017 19:55:07) release log
00:00:00.000000 main Log opened 2019-11-25T10:00:40.549362900Z
00:00:00.000000 main Build Type: release
00:00:00.000000 main OS Product: Windows 10
00:00:00.000000 main OS Release: 10.0.18363
00:00:00.000000 main OS Service Pack:
00:00:00.015624 main DMI Product Name: X99-DELUXE
00:00:00.031247 main DMI Product Version: X99-DELUXE
00:00:00.031247 main Host RAM: 8093MB total, 6222MB available
00:00:00.031247 main Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.031247 main Process ID: 6732
00:00:00.031247 main Package type: WINDOWS_64BITS_GENERIC
00:00:00.031247 Home directory: 'C:\ProgramData\BOINC\projects\virtualbox'
00:00:00.031247 Installed Drivers:
00:00:00.031247 C:\WINDOWS\system32\DRIVERS\VBoxNetAdp6.sys (Version: 5.0.40.15130)
00:00:00.031247 C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.0.40.15130)
00:00:00.031247 C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.0.40.15130)
00:00:00.031247 C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.0.40.15130)
00:00:00.031247 Loading settings file "C:\ProgramData\BOINC\projects\virtualbox\VirtualBox.xml" with version "1.12-windows"
00:00:00.031247 Getting USB descriptor failed with error 31
00:00:00.173828 USB: Unknown USB device detected (idVendor: 0x0b05, idProduct: 0x180a). Please, report the idVendor and idProduct to virtualbox.org.
00:00:00.220706 HostDnsMonitor: old information
00:00:00.220706 no server entries
00:00:00.220706 no domain set
00:00:00.220706 no search string entries
00:00:00.220706 HostDnsMonitor: new information
00:00:00.220706 server 1: 172.22.8.1
00:00:00.220706 server 2: 193.190.198.2
00:00:00.220706 server 3: 193.190.198.10
00:00:00.220706 domain: example.org
00:00:00.220706 search string 1: example.org
00:00:00.220706 search string 2: fedpol.local
00:00:00.220706 HostDnsMonitorProxy::notify
00:00:00.287479 VD: VDInit finished
00:00:00.287479 Loading settings file "C:\ProgramData\BOINC\slots\8\boinc_a319cc6e207193ae\boinc_a319cc6e207193ae.vbox" with version "1.15-windows"
00:00:00.287479 Loading settings file "C:\ProgramData\BOINC\slots\19\boinc_ccdaa543bf0ecbcb\boinc_ccdaa543bf0ecbcb.vbox" with version "1.15-windows"
00:00:01.332134 Watcher ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={MachineWrap} aText={The virtual machine 'boinc_a319cc6e207193ae' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\ProgramData\BOINC\slots\8\boinc_a319cc6e207193ae\Logs\VBoxHardening.log'}, preserve=false aResultDetail=0
VM Execution Log:
VM Startup Log:
VM Trace Log:
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-22 08:08:13 (13476):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-22 08:09:03 (13476):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-22 08:09:52 (13476):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-22 08:10:41 (13476):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-22 08:11:30 (13476):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-22 08:12:19 (13476):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-22 08:13:06 (13476):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-22 08:13:54 (13476):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-23 08:14:26 (11864):
Command: "VBoxSVC.exe" --logrotate 1
Exit Code: 0
Output:
2019-11-23 08:14:26 (11864):
Command: VBoxManage -q --version
Exit Code: 0
Output:
6.0.14r133895
2019-11-23 08:14:26 (11864):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-23 08:14:28 (11864):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-23 08:14:29 (11864):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-23 08:14:30 (11864):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-23 08:15:20 (11864):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-23 08:16:10 (11864):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-23 08:16:59 (11864):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-23 08:17:49 (11864):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-23 08:18:39 (11864):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-23 08:19:29 (11864):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-23 08:20:19 (11864):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-23 08:21:09 (11864):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-24 08:21:19 (9756):
Command: "VBoxSVC.exe" --logrotate 1
Exit Code: 0
Output:
2019-11-24 08:21:19 (9756):
Command: VBoxManage -q --version
Exit Code: 0
Output:
6.0.14r133895
2019-11-24 08:21:20 (9756):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-24 08:21:21 (9756):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-24 08:21:22 (9756):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-24 08:21:23 (9756):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-24 08:22:13 (9756):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-24 08:23:04 (9756):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-24 08:23:53 (9756):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-24 08:24:43 (9756):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-24 08:25:33 (9756):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-24 08:26:23 (9756):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-24 08:27:13 (9756):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-24 08:28:03 (9756):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-25 08:28:42 (13076):
Command: "VBoxSVC.exe" --logrotate 1
Exit Code: 0
Output:
2019-11-25 08:28:42 (13076):
Command: VBoxManage -q --version
Exit Code: 0
Output:
6.0.14r133895
2019-11-25 08:28:43 (13076):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-25 08:28:44 (13076):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-25 08:28:45 (13076):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-25 08:28:46 (13076):
Command: VBoxManage -q list systemproperties
Exit Code: -2147024891
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-25 08:29:36 (13076):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-25 08:30:24 (13076):
Command: VBoxManage -q list systemproperties
Exit Code: -182
Output:
2019-11-25 08:31:14 (13076):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-25 08:32:04 (13076):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-25 08:32:54 (13076):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-25 08:33:44 (13076):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-25 08:34:34 (13076):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
2019-11-25 08:35:24 (13076):
Command: VBoxManage -q list hostinfo
Exit Code: -182
Output:
VM Exit Code: 259 (0x103)
2019-11-25 12:07:20 (7520): vboxwrapper (7.9.26200): starting
2019-11-25 12:07:20 (7520): Status Report: Launching vboxsvc.exe. (PID = '7636')
2019-11-25 12:09:05 (7520): Error in guest additions for VM: -182
Command:
VBoxManage -q list systemproperties
Output:
2019-11-25 12:09:05 (7520): Feature: Checkpoint interval offset (450 seconds)
2019-11-25 12:09:05 (7520): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-25 12:09:05 (7520): Detected: Sandbox Configuration Enabled
2019-11-25 12:12:21 (7520): Error in host info for VM: -2147024891
Command:
VBoxManage -q list hostinfo
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-25 12:12:21 (7520): WARNING: Communication with VM Hypervisor failed.
2019-11-25 12:12:21 (7520): Could not communicate with VM Hypervisor. Rescheduling execution for a later date.
2019-11-25 12:32:10 (7676): vboxwrapper (7.9.26200): starting
2019-11-25 12:32:10 (7676): Status Report: Launching vboxsvc.exe. (PID = '7744')
2019-11-25 12:32:11 (7676): Feature: Checkpoint interval offset (459 seconds)
2019-11-25 12:32:11 (7676): Detected: VirtualBox VboxManage Interface (Version: 6.0.14)
2019-11-25 12:32:11 (7676): Detected: Sandbox Configuration Enabled
2019-11-25 12:32:12 (7676): Detected: Minimum checkpoint interval (600.000000 seconds)
2019-11-25 12:32:12 (7676): Starting VM using VboxManage interface. (boinc_a319cc6e207193ae, slot#8)
2019-11-25 12:32:17 (7676): Successfully started VM. (PID = '8460')
2019-11-25 12:32:17 (7676): Reporting VM Process ID to BOINC.
2019-11-25 12:32:22 (7676): Guest Log: BIOS: VirtualBox 6.0.14
2019-11-25 12:32:22 (7676): Guest Log: CPUID EDX: 0x178bfbff
2019-11-25 12:32:22 (7676): Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
2019-11-25 12:32:22 (7676): Guest Log: int13_harddisk: function 02, unmapped device for ELDL=80
2019-11-25 12:32:22 (7676): Guest Log: BIOS: Boot from Hard Disk 0 failed
2019-11-25 12:32:22 (7676): Guest Log: BIOS: Boot : bseqnr=2, bootseq=0003
2019-11-25 12:32:22 (7676): Guest Log: BIOS: Booting from CD-ROM...
2019-11-25 12:32:22 (7676): Guest Log: BIOS: KBD: unsupported int 16h function 03
2019-11-25 12:32:22 (7676): Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
2019-11-25 12:32:22 (7676): VM state change detected. (old = 'poweroff', new = 'running')
2019-11-25 12:32:27 (7676): Guest Log: vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
2019-11-25 12:32:27 (7676): Guest Log: vboxguest: misc device minor 56, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
2019-11-25 12:32:27 (7676): Guest Log: net.ipv4.ip_forward = 1
2019-11-25 12:32:27 (7676): Guest Log: sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
2019-11-25 12:32:27 (7676): Guest Log: sysctl: setting key "cannot stat %s": No such file or directory
2019-11-25 12:32:27 (7676): Guest Log: sysctl: "cannot stat %s" is an unknown key
2019-11-25 12:32:27 (7676): Guest Log: sysctl: setting key "cannot stat %s": No such file or directory
2019-11-25 12:32:27 (7676): Guest Log: Segmentation fault
2019-11-25 12:32:27 (7676): Guest Log: automount ...
2019-11-25 12:32:27 (7676): Guest Log: Is the disk unpartitioned?, test for the 'boot2docker format-me' string
2019-11-25 12:32:27 (7676): Guest Log: automount over.
2019-11-25 12:32:27 (7676): Guest Log: [1;32mSetting hostname to [1;35mboot2docker[0;39m [1;32mDone.[0;39m
2019-11-25 12:32:27 (7676): Guest Log: Mon Nov 25 12:32:25 UTC 2019 dhcp -------------------------------
2019-11-25 12:32:33 (7676): Guest Log: udevadm settle - timeout of 5 seconds reached, the event queue contains:
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0700:00 (1081)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00 (1307)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXCPU:00 (1308)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXPWRBN:00 (1309)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 (1310)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0 (1311)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSLPBN:00 (1312)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1 (1313)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1/event1 (1314)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00 (1315)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 (1316)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00 (1317)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00/power_supply/AC (1318)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00 (1319)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/device:01 (1320)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7 (1321)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7/event5 (1322)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0400:00 (1323)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0400:01 (1324)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:00 (1325)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:01 (1326)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:02 (1327)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:03 (1328)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:00 (1329)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C0A:00 (1330)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP8390:00 (1331)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00 (1332)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/APP0001:00 (1333)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0000:00 (1334)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0100:00 (1335)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0103:00 (1336)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0200:00 (1337)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0303:00 (1338)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0700:00 (1339)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0B00:00 (1340)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0F03:00 (1341)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02 (1342)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:00 (1343)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:01 (1344)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:02 (1345)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:03 (1346)
2019-11-25 12:32:33 (7676): Guest Log: /sys/devices/LNXSYSTM:00/LNXSYBUS:01 (1347)
2019-11-25 12:32:33 (7676): Preference change detected
2019-11-25 12:32:33 (7676): Setting CPU throttle for VM. (100%)
2019-11-25 12:32:33 (7676): Setting checkpoint interval to 600 seconds. (Higher value of (Preference: 600 seconds) or (Vbox_job.xml: 600 seconds))
2019-11-25 12:32:38 (7676): Guest Log: Mon Nov 25 12:32:31 UTC 2019 dhcp -------------------------------
2019-11-25 12:32:38 (7676): Guest Log: VBoxService 5.0.16 r105871 (verbosity: 0) linux.amd64 (Mar 4 2016 17:38:55) release log
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.000056 main Log opened 2019-11-25T12:32:31.703328000Z
2019-11-25 12:32:38 (7676): Guest Log: VBoxService 5.0.16 r105871 (verbosity: 0) linux.amd64 (Mar 4 2016 17:38:55) release log
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.000056 main Log opened 2019-11-25T12:32:31.703328000Z
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002084 main OS Product: Linux
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002128 main OS Release: 4.1.19-boot2docker
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002159 main OS Version: #1 SMP Sun Apr 17 19:40:54 UTC 2016
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002188 main Executable: /sbin/VBoxService
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002189 main Process ID: 914
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002190 main Package type: LINUX_64BITS_GENERIC
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002084 main OS Product: Linux
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002128 main OS Release: 4.1.19-boot2docker
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002159 main OS Version: #1 SMP Sun Apr 17 19:40:54 UTC 2016
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002188 main Executable: /sbin/VBoxService
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002189 main Process ID: 914
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.002190 main Package type: LINUX_64BIT00:00:00.006539 main 5.0.16 r105871 started. Verbose level = 0
2019-11-25 12:32:38 (7676): Guest Log: S_GENERIC
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.006539 main 5.0.16 r105871 started. Verbose level = 0
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.009378 vminfo rtldrNativeLoad: dlopen('libdbus-1.so.3', RTLD_NOW | RTLD_LOCAL) failed: libdbus-1.so.3: cannot open shared object file: No such file or directory
2019-11-25 12:32:38 (7676): Guest Log: 00:00:00.009429 vminfo Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
2019-11-25 12:32:38 (7676): Guest Log: Mounting BOINC shared/...
2019-11-25 12:32:38 (7676): Guest Log: -------------------
2019-11-25 12:32:38 (7676): Guest Log: Mon Nov 25 11:32:33 UTC 2019
2019-11-25 12:32:44 (7676): Guest Log: 00:00:05.009838 vminfo Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
2019-11-25 12:32:44 (7676): Guest Log: Mon Nov 25 11:32:38 UTC 2019
2019-11-25 12:32:44 (7676): Guest Log: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
2019-11-25 12:32:44 (7676): Guest Log: link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2019-11-25 12:32:44 (7676): Guest Log: inet 127.0.0.1/8 scope host lo
2019-11-25 12:32:44 (7676): Guest Log: valid_lft forever preferred_lft forever
2019-11-25 12:32:44 (7676): Guest Log: inet6 ::1/128 scope host
2019-11-25 12:32:44 (7676): Guest Log: valid_lft forever preferred_lft forever
2019-11-25 12:32:44 (7676): Guest Log: 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
2019-11-25 12:32:44 (7676): Guest Log: link/ether 42:68:39:9b:a7:dd brd ff:ff:ff:ff:ff:ff
2019-11-25 12:32:44 (7676): Guest Log: 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
2019-11-25 12:32:44 (7676): Guest Log: link/ether 08:00:27:82:b6:f1 brd ff:ff:ff:ff:ff:ff
2019-11-25 12:32:44 (7676): Guest Log: inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
2019-11-25 12:32:44 (7676): Guest Log: valid_lft forever preferred_lft forever
2019-11-25 12:32:44 (7676): Guest Log: inet6 fe80::a00:27ff:fe82:b6f1/64 scope link
2019-11-25 12:32:44 (7676): Guest Log: valid_lft forever preferred_lft forever
2019-11-25 12:32:44 (7676): Guest Log: -------------------
2019-11-25 12:32:44 (7676): Guest Log: Linking /etc/docker to /var/lib/boot2docker for persistence
2019-11-25 12:32:44 (7676): Guest Log: Waiting for Docker daemon to start...
2019-11-25 12:32:44 (7676): Guest Log: REPOSITORY TAG IMAGE ID CREATED SIZE
2019-11-25 12:32:44 (7676): Guest Log: Running boinc_app...
2019-11-25 12:32:44 (7676): Guest Log: Importing Docker image from BOINC...
2019-11-25 12:32:44 (7676): Guest Log: Filesystem Size Used Available Use% Mounted on
2019-11-25 12:32:44 (7676): Guest Log: tmpfs 2.6G 164.2M 2.5G 6% /
2019-11-25 12:32:44 (7676): Guest Log: tmpfs 1.5G 0 1.5G 0% /dev/shm
2019-11-25 12:32:44 (7676): Guest Log: cgroup 1.5G 0 1.5G 0% /sys/fs/cgroup
2019-11-25 12:32:44 (7676): Guest Log: shared 475.9G 74.4G 401.6G 16% /root/shared
2019-11-25 12:32:44 (7676): Guest Log: tmpfs 2.6G 164.2M 2.5G 6% /var/lib/docker/aufs
2019-11-25 12:32:44 (7676): Guest Log: 00:00:10.012471 vminfo Error: Unable to connect to system D-Bus (3/3): D-Bus not installed
2019-11-25 12:32:49 (7676): Guest Log: doing docker load...
2019-11-25 12:33:05 (7676): Guest Log: Filesystem Size Used Available Use% Mounted on
2019-11-25 12:33:05 (7676): Guest Log: tmpfs 2.6G 721.5M 1.9G 27% /
2019-11-25 12:33:05 (7676): Guest Log: tmpfs 1.5G 0 1.5G 0% /dev/shm
2019-11-25 12:33:05 (7676): Guest Log: cgroup 1.5G 0 1.5G 0% /sys/fs/cgroup
2019-11-25 12:33:05 (7676): Guest Log: shared 475.9G 74.0G 402.0G 16% /root/shared
2019-11-25 12:33:05 (7676): Guest Log: tmpfs 2.6G 721.5M 1.9G 27% /var/lib/docker/aufs
2019-11-25 12:33:05 (7676): Guest Log: total used free shared buff/cache available
2019-11-25 12:33:05 (7676): Guest Log: Mem: 3007 49 2195 721 762 2196
2019-11-25 12:33:05 (7676): Guest Log: Swap: 698 0 698
2019-11-25 12:33:05 (7676): Guest Log: Building apps directory...
2019-11-25 12:34:13 (7676): Guest Log: Prerun diagnostics...
2019-11-25 12:34:13 (7676): Guest Log: REPOSITORY TAG IMAGE ID CREATED SIZE
2019-11-25 12:34:13 (7676): Guest Log: nanohub_apps_share64_octave 5 a3c939485731 23 months ago 547 MB
2019-11-25 12:34:13 (7676): Guest Log: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2019-11-25 12:34:13 (7676): Guest Log: 557.4M /var/lib/docker
2019-11-25 12:34:13 (7676): Guest Log: total used free shared buff/cache available
2019-11-25 12:34:13 (7676): Guest Log: Mem: 3007 50 2190 721 766 2194
2019-11-25 12:34:13 (7676): Guest Log: Swap: 698 0 698
2019-11-25 12:34:13 (7676): Guest Log: Filesystem Size Used Available Use% Mounted on
2019-11-25 12:34:13 (7676): Guest Log: tmpfs 2.6G 721.5M 1.9G 27% /
2019-11-25 12:34:13 (7676): Guest Log: tmpfs 1.5G 0 1.5G 0% /dev/shm
2019-11-25 12:34:13 (7676): Guest Log: cgroup 1.5G 0 1.5G 0% /sys/fs/cgroup
2019-11-25 12:34:13 (7676): Guest Log: shared 475.9G 75.0G 400.9G 16% /root/shared
2019-11-25 12:34:13 (7676): Guest Log: tmpfs 2.6G 721.5M 1.9G 27% /var/lib/docker/aufs
2019-11-25 12:34:13 (7676): Guest Log: Running...
2019-11-25 12:34:13 (7676): Guest Log: 07560052_16.boinc
2019-11-25 12:34:13 (7676): Guest Log: 07560052_16.sh
2019-11-25 12:36:30 (7676): Guest Log: boinc_app exited (0)
2019-11-25 12:36:30 (7676): Guest Log: Saving results...
2019-11-25 12:36:30 (7676): Guest Log: 07560052_16_output.tar.gz
2019-11-25 12:36:30 (7676): VM Completion File Detected.
2019-11-25 12:36:30 (7676): Powering off VM.
2019-11-25 12:36:31 (7676): Successfully stopped VM.
2019-11-25 12:36:31 (7676): Deregistering VM. (boinc_a319cc6e207193ae, slot#8)
2019-11-25 12:36:31 (7676): Removing network bandwidth throttle group from VM.
2019-11-25 12:36:31 (7676): Removing VM from VirtualBox.
2019-11-25 12:36:31 (7676): Removing virtual ISO 9660 disk from VirtualBox.
12:36:37 (7676): called boinc_finish(0)
</stderr_txt>
]]>
©2024 COPYRIGHT 2017-2018 NCN