Problems and Technical Issues with Rosetta@home

Message boards : Number crunching : Problems and Technical Issues with Rosetta@home

To post messages, you must log in.

Previous · 1 . . . 153 · 154 · 155 · 156 · 157 · 158 · 159 . . . 309 · Next

AuthorMessage
Mr P Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 1600
Credit: 12,116,986
RAC: 12,028
Message 104100 - Posted: 9 Jan 2022, 19:46:49 UTC - in response to Message 104098.  

Maybe download a fresh copy of Vbox and then "repair" Vbox. That's about all there is left to do that I can think of.
I've done that many times, and tried three different versions. I have 7 PCs, and only 1 works, so it's nothing particularly wrong with one.

I don't know if chip drivers make any difference to data crunching or not.
I am out of ideas at this point in time.
If so it's very fussy. From the 7 PCs I'm using all I can conclude is AMD doesn't work and older Intel doesn't work.

Your tasks never get suspended for lack of memory or unstable VM environment?
Do you shut down your system at any time?
If so how?
No, that system only runs Boinc. I booted it up, installed a fresh Vbox, attached to Rosetta, got tasks, and even tried just one at a time, but it ticked over for 24 hours without any processing time at all. It has 36GB of RAM, so should have run a single one easily.
ID: 104100 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mr P Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 1600
Credit: 12,116,986
RAC: 12,028
Message 104101 - Posted: 9 Jan 2022, 21:07:04 UTC - in response to Message 104100.  
Last modified: 9 Jan 2022, 21:08:16 UTC

Just had my first error on the good machine.

<core_client_version>7.16.20</core_client_version>
<![CDATA[
<message>
aborted by user</message>
<stderr_txt>
2022-01-09 10:00:48 (9148): Detected: vboxwrapper 26202
2022-01-09 10:00:48 (9148): Detected: BOINC client v7.16.20
2022-01-09 10:00:49 (9148): Detected: VirtualBox VboxManage Interface (Version: 5.2.44)
2022-01-09 10:00:49 (9148): Feature: Checkpoint interval offset (547 seconds)
2022-01-09 10:00:49 (9148): Detected: Minimum checkpoint interval (600.000000 seconds)
2022-01-09 10:00:50 (9148): Create VM. (boinc_bfaf948f1cde7377, slot#4)
2022-01-09 10:00:51 (9148): Setting Memory Size for VM. (6144MB)
2022-01-09 10:00:51 (9148): Setting CPU Count for VM. (1)
2022-01-09 10:00:51 (9148): Setting Chipset Options for VM.
2022-01-09 10:00:51 (9148): Setting Boot Options for VM.
2022-01-09 10:00:52 (9148): Setting Network Configuration for NAT.
2022-01-09 10:00:52 (9148): Disabling VM Network Access.
2022-01-09 10:00:52 (9148): Disabling USB Support for VM.
2022-01-09 10:00:52 (9148): Disabling COM Port Support for VM.
2022-01-09 10:00:53 (9148): Disabling LPT Port Support for VM.
2022-01-09 10:00:53 (9148): Disabling Audio Support for VM.
2022-01-09 10:00:53 (9148): Disabling Clipboard Support for VM.
2022-01-09 10:00:54 (9148): Disabling Drag and Drop Support for VM.
2022-01-09 10:00:54 (9148): Adding storage controller(s) to VM.
2022-01-09 10:00:54 (9148): Adding virtual disk drive to VM. (vm_image.vdi)
2022-01-09 10:00:54 (9148): Adding VirtualBox Guest Additions to VM.
2022-01-09 10:00:55 (9148): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB)
2022-01-09 10:00:55 (9148): Enabling shared directory for VM.
2022-01-09 10:00:55 (9148): Starting VM using VBoxManage interface. (boinc_bfaf948f1cde7377, slot#4)
2022-01-09 10:01:02 (9148): Successfully started VM. (PID = '13352')
2022-01-09 10:01:02 (9148): Reporting VM Process ID to BOINC.
2022-01-09 10:01:02 (9148): Guest Log: BIOS: VirtualBox 5.2.44
2022-01-09 10:01:02 (9148): Guest Log: CPUID EDX: 0x078bfbff
2022-01-09 10:01:02 (9148): Guest Log: BIOS: ata0-0: PCHS=16383/16/63 LCHS=1024/255/63
2022-01-09 10:01:02 (9148): VM state change detected. (old = 'poweredoff', new = 'running')
2022-01-09 10:01:02 (9148): Preference change detected
2022-01-09 10:01:02 (9148): Setting CPU throttle for VM. (100%)
2022-01-09 10:01:02 (9148): Setting checkpoint interval to 600 seconds. (Higher value of (Preference: 60 seconds) or (Vbox_job.xml: 600 seconds))
2022-01-09 10:01:04 (9148): Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
2022-01-09 10:01:04 (9148): Guest Log: BIOS: Booting from Hard Disk...
2022-01-09 10:20:10 (9148): Creating new snapshot for VM.
2022-01-09 10:20:12 (9148): Checkpoint completed.
2022-01-09 10:30:11 (9148): Creating new snapshot for VM.
2022-01-09 10:30:13 (9148): Deleting stale snapshot.
2022-01-09 10:30:13 (9148): Checkpoint completed.
2022-01-09 10:40:12 (9148): Creating new snapshot for VM.
2022-01-09 10:40:13 (9148): Deleting stale snapshot.
2022-01-09 10:40:13 (9148): Checkpoint completed.
2022-01-09 10:50:13 (9148): Creating new snapshot for VM.
2022-01-09 10:50:14 (9148): Deleting stale snapshot.
2022-01-09 10:50:15 (9148): Checkpoint completed.
2022-01-09 11:00:14 (9148): Creating new snapshot for VM.
2022-01-09 11:00:15 (9148): Deleting stale snapshot.
2022-01-09 11:00:16 (9148): Checkpoint completed.
2022-01-09 11:10:15 (9148): Creating new snapshot for VM.
2022-01-09 11:10:16 (9148): Deleting stale snapshot.
2022-01-09 11:10:17 (9148): Checkpoint completed.
2022-01-09 11:20:16 (9148): Creating new snapshot for VM.
2022-01-09 11:20:18 (9148): Deleting stale snapshot.
2022-01-09 11:20:18 (9148): Checkpoint completed.
2022-01-09 11:30:17 (9148): Creating new snapshot for VM.
2022-01-09 11:30:27 (9148): Deleting stale snapshot.
2022-01-09 11:30:28 (9148): Checkpoint completed.
2022-01-09 11:40:18 (9148): Creating new snapshot for VM.
2022-01-09 11:40:19 (9148): Deleting stale snapshot.
2022-01-09 11:40:19 (9148): Checkpoint completed.
2022-01-09 11:41:05 (9148): Status Report: Elapsed Time: '6000.294384'
2022-01-09 11:41:05 (9148): Status Report: CPU Time: '12.875000'
2022-01-09 11:50:19 (9148): Creating new snapshot for VM.
2022-01-09 11:50:20 (9148): Deleting stale snapshot.
2022-01-09 11:50:20 (9148): Checkpoint completed.
2022-01-09 12:00:20 (9148): Creating new snapshot for VM.
2022-01-09 12:00:21 (9148): Deleting stale snapshot.
2022-01-09 12:00:21 (9148): Checkpoint completed.
2022-01-09 12:10:21 (9148): Creating new snapshot for VM.
2022-01-09 12:10:22 (9148): Deleting stale snapshot.
2022-01-09 12:10:23 (9148): Checkpoint completed.
2022-01-09 12:20:22 (9148): Creating new snapshot for VM.
2022-01-09 12:20:24 (9148): Deleting stale snapshot.
2022-01-09 12:20:25 (9148): Checkpoint completed.
2022-01-09 12:30:23 (9148): Creating new snapshot for VM.
2022-01-09 12:30:24 (9148): Deleting stale snapshot.
2022-01-09 12:30:25 (9148): Checkpoint completed.
2022-01-09 12:40:24 (9148): Creating new snapshot for VM.
2022-01-09 12:40:25 (9148): Deleting stale snapshot.
2022-01-09 12:40:26 (9148): Checkpoint completed.
2022-01-09 12:50:25 (9148): Creating new snapshot for VM.
2022-01-09 12:50:26 (9148): Deleting stale snapshot.
2022-01-09 12:50:27 (9148): Checkpoint completed.
2022-01-09 13:00:25 (9148): Creating new snapshot for VM.
2022-01-09 13:00:28 (9148): Deleting stale snapshot.
2022-01-09 13:00:28 (9148): Checkpoint completed.
2022-01-09 13:10:26 (9148): Creating new snapshot for VM.
2022-01-09 13:10:27 (9148): Deleting stale snapshot.
2022-01-09 13:10:28 (9148): Checkpoint completed.
2022-01-09 13:20:27 (9148): Creating new snapshot for VM.
2022-01-09 13:20:28 (9148): Deleting stale snapshot.
2022-01-09 13:20:29 (9148): Checkpoint completed.
2022-01-09 13:21:09 (9148): Status Report: Elapsed Time: '12000.424887'
2022-01-09 13:21:09 (9148): Status Report: CPU Time: '21.531250'
2022-01-09 13:30:28 (9148): Creating new snapshot for VM.
2022-01-09 13:30:30 (9148): Deleting stale snapshot.
2022-01-09 13:30:30 (9148): Checkpoint completed.
2022-01-09 13:40:29 (9148): Creating new snapshot for VM.
2022-01-09 13:40:31 (9148): Deleting stale snapshot.
2022-01-09 13:40:31 (9148): Checkpoint completed.
2022-01-09 13:50:30 (9148): Creating new snapshot for VM.
2022-01-09 13:50:32 (9148): Deleting stale snapshot.
2022-01-09 13:50:32 (9148): Checkpoint completed.
2022-01-09 14:00:31 (9148): Creating new snapshot for VM.
2022-01-09 14:00:33 (9148): Deleting stale snapshot.
2022-01-09 14:00:33 (9148): Checkpoint completed.
2022-01-09 14:10:33 (9148): Creating new snapshot for VM.
2022-01-09 14:10:34 (9148): Deleting stale snapshot.
2022-01-09 14:10:34 (9148): Checkpoint completed.
2022-01-09 14:20:34 (9148): Creating new snapshot for VM.
2022-01-09 14:20:35 (9148): Deleting stale snapshot.
2022-01-09 14:20:36 (9148): Checkpoint completed.
2022-01-09 14:30:35 (9148): Creating new snapshot for VM.
2022-01-09 14:30:36 (9148): Deleting stale snapshot.
2022-01-09 14:30:37 (9148): Checkpoint completed.
2022-01-09 14:40:36 (9148): Creating new snapshot for VM.
2022-01-09 14:40:38 (9148): Deleting stale snapshot.
2022-01-09 14:40:38 (9148): Checkpoint completed.
2022-01-09 14:50:37 (9148): Creating new snapshot for VM.
2022-01-09 14:50:38 (9148): Deleting stale snapshot.
2022-01-09 14:50:39 (9148): Checkpoint completed.
2022-01-09 15:00:37 (9148): Creating new snapshot for VM.
2022-01-09 15:00:39 (9148): Deleting stale snapshot.
2022-01-09 15:00:40 (9148): Checkpoint completed.
2022-01-09 15:01:13 (9148): Status Report: Elapsed Time: '18000.783836'
2022-01-09 15:01:13 (9148): Status Report: CPU Time: '30.671875'
2022-01-09 15:10:38 (9148): Creating new snapshot for VM.
2022-01-09 15:10:39 (9148): Deleting stale snapshot.
2022-01-09 15:10:40 (9148): Checkpoint completed.
2022-01-09 15:20:39 (9148): Creating new snapshot for VM.
2022-01-09 15:20:41 (9148): Deleting stale snapshot.
2022-01-09 15:20:43 (9148): Checkpoint completed.
2022-01-09 15:30:40 (9148): Creating new snapshot for VM.
2022-01-09 15:30:42 (9148): Deleting stale snapshot.
2022-01-09 15:30:43 (9148): Checkpoint completed.
2022-01-09 15:40:40 (9148): Creating new snapshot for VM.
2022-01-09 15:40:42 (9148): Deleting stale snapshot.
2022-01-09 15:40:43 (9148): Checkpoint completed.
2022-01-09 15:50:41 (9148): Creating new snapshot for VM.
2022-01-09 15:50:44 (9148): Deleting stale snapshot.
2022-01-09 15:50:45 (9148): Checkpoint completed.
2022-01-09 16:00:42 (9148): Creating new snapshot for VM.
2022-01-09 16:00:44 (9148): Deleting stale snapshot.
2022-01-09 16:00:45 (9148): Checkpoint completed.
2022-01-09 16:10:42 (9148): Creating new snapshot for VM.
2022-01-09 16:10:51 (9148): Deleting stale snapshot.
2022-01-09 16:10:52 (9148): Checkpoint completed.
2022-01-09 16:20:43 (9148): Creating new snapshot for VM.
2022-01-09 16:20:45 (9148): Deleting stale snapshot.
2022-01-09 16:20:46 (9148): Checkpoint completed.
2022-01-09 16:30:44 (9148): Creating new snapshot for VM.
2022-01-09 16:30:46 (9148): Deleting stale snapshot.
2022-01-09 16:30:48 (9148): Checkpoint completed.
2022-01-09 16:40:45 (9148): Creating new snapshot for VM.
2022-01-09 16:40:47 (9148): Deleting stale snapshot.
2022-01-09 16:40:48 (9148): Checkpoint completed.
2022-01-09 16:41:16 (9148): Status Report: Elapsed Time: '24000.936079'
2022-01-09 16:41:16 (9148): Status Report: CPU Time: '40.015625'
2022-01-09 16:50:45 (9148): Creating new snapshot for VM.
2022-01-09 16:50:48 (9148): Deleting stale snapshot.
2022-01-09 16:50:49 (9148): Checkpoint completed.
2022-01-09 17:00:46 (9148): Creating new snapshot for VM.
2022-01-09 17:00:48 (9148): Deleting stale snapshot.
2022-01-09 17:00:49 (9148): Checkpoint completed.
2022-01-09 17:10:46 (9148): Creating new snapshot for VM.
2022-01-09 17:10:49 (9148): Deleting stale snapshot.
2022-01-09 17:10:50 (9148): Checkpoint completed.
2022-01-09 17:20:47 (9148): Creating new snapshot for VM.
2022-01-09 17:20:49 (9148): Deleting stale snapshot.
2022-01-09 17:20:50 (9148): Checkpoint completed.
2022-01-09 17:30:47 (9148): Creating new snapshot for VM.
2022-01-09 17:30:49 (9148): Deleting stale snapshot.
2022-01-09 17:30:49 (9148): Checkpoint completed.
2022-01-09 17:40:48 (9148): Creating new snapshot for VM.
2022-01-09 17:40:50 (9148): Deleting stale snapshot.
2022-01-09 17:40:50 (9148): Checkpoint completed.
2022-01-09 17:50:49 (9148): Creating new snapshot for VM.
2022-01-09 17:50:51 (9148): Deleting stale snapshot.
2022-01-09 17:50:51 (9148): Checkpoint completed.
2022-01-09 18:00:50 (9148): Creating new snapshot for VM.
2022-01-09 18:00:51 (9148): Deleting stale snapshot.
2022-01-09 18:00:52 (9148): Checkpoint completed.
2022-01-09 18:10:50 (9148): Creating new snapshot for VM.
2022-01-09 18:10:52 (9148): Deleting stale snapshot.
2022-01-09 18:10:52 (9148): Checkpoint completed.
2022-01-09 18:20:51 (9148): Creating new snapshot for VM.
2022-01-09 18:20:53 (9148): Deleting stale snapshot.
2022-01-09 18:20:53 (9148): Checkpoint completed.
2022-01-09 18:21:20 (9148): Status Report: Elapsed Time: '30001.861790'
2022-01-09 18:21:20 (9148): Status Report: CPU Time: '48.890625'
2022-01-09 18:30:52 (9148): Creating new snapshot for VM.
2022-01-09 18:30:54 (9148): Deleting stale snapshot.
2022-01-09 18:30:54 (9148): Checkpoint completed.
2022-01-09 18:40:54 (9148): Creating new snapshot for VM.
2022-01-09 18:40:57 (9148): Deleting stale snapshot.
2022-01-09 18:40:58 (9148): Checkpoint completed.
2022-01-09 18:50:55 (9148): Creating new snapshot for VM.
2022-01-09 18:50:56 (9148): Deleting stale snapshot.
2022-01-09 18:50:57 (9148): Checkpoint completed.
2022-01-09 19:00:56 (9148): Creating new snapshot for VM.
2022-01-09 19:00:58 (9148): Deleting stale snapshot.
2022-01-09 19:00:58 (9148): Checkpoint completed.
2022-01-09 19:10:57 (9148): Creating new snapshot for VM.
2022-01-09 19:10:59 (9148): Deleting stale snapshot.
2022-01-09 19:10:59 (9148): Checkpoint completed.
2022-01-09 19:20:59 (9148): Creating new snapshot for VM.
2022-01-09 19:21:00 (9148): Deleting stale snapshot.
2022-01-09 19:21:01 (9148): Checkpoint completed.
2022-01-09 19:30:59 (9148): Creating new snapshot for VM.
2022-01-09 19:31:01 (9148): Deleting stale snapshot.
2022-01-09 19:31:01 (9148): Checkpoint completed.
2022-01-09 19:41:00 (9148): Creating new snapshot for VM.
2022-01-09 19:41:01 (9148): Deleting stale snapshot.
2022-01-09 19:41:02 (9148): Checkpoint completed.
2022-01-09 19:51:00 (9148): Creating new snapshot for VM.
2022-01-09 19:51:02 (9148): Deleting stale snapshot.
2022-01-09 19:51:02 (9148): Checkpoint completed.
2022-01-09 20:01:01 (9148): Creating new snapshot for VM.
2022-01-09 20:01:04 (9148): Deleting stale snapshot.
2022-01-09 20:01:05 (9148): Checkpoint completed.
2022-01-09 20:01:24 (9148): Status Report: Elapsed Time: '36002.522949'
2022-01-09 20:01:24 (9148): Status Report: CPU Time: '58.187500'
2022-01-09 20:11:02 (9148): Creating new snapshot for VM.
2022-01-09 20:11:04 (9148): Deleting stale snapshot.
2022-01-09 20:11:04 (9148): Checkpoint completed.
2022-01-09 20:21:03 (9148): Creating new snapshot for VM.
2022-01-09 20:21:05 (9148): Deleting stale snapshot.
2022-01-09 20:21:05 (9148): Checkpoint completed.
2022-01-09 20:31:05 (9148): Creating new snapshot for VM.
2022-01-09 20:31:06 (9148): Deleting stale snapshot.
2022-01-09 20:31:07 (9148): Checkpoint completed.
2022-01-09 20:37:40 (9148): Preference change detected
2022-01-09 20:37:40 (9148): Setting CPU throttle for VM. (100%)
2022-01-09 20:37:40 (9148): Setting checkpoint interval to 600 seconds. (Higher value of (Preference: 60 seconds) or (Vbox_job.xml: 600 seconds))
2022-01-09 20:41:06 (9148): Creating new snapshot for VM.
2022-01-09 20:41:07 (9148): Deleting stale snapshot.
2022-01-09 20:41:08 (9148): Checkpoint completed.
2022-01-09 20:50:47 (9148): Powering off VM.
2022-01-09 20:50:48 (9148): Successfully stopped VM.
2022-01-09 20:50:48 (9148): Deregistering VM. (boinc_bfaf948f1cde7377, slot#4)
2022-01-09 20:50:48 (9148): Deleting stale snapshot.
2022-01-09 20:50:49 (9148): Removing network bandwidth throttle group from VM.
2022-01-09 20:50:49 (9148): Removing VM from VirtualBox.

Hypervisor System Log:

42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.338033 DeleteSnap ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=true aResultDetail=0
42:57:17.339006 DeleteSnap Saving settings file "C:ProgramDataBOINCslots4boinc_bfaf948f1cde7377boinc_bfaf948f1cde7377.vbox" with version "1.16-windows"
42:57:17.476622 DeleteSnap Saving settings file "C:ProgramDataBOINCslots4boinc_bfaf948f1cde7377boinc_bfaf948f1cde7377.vbox" with version "1.16-windows"
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.634734 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.637660 Saving settings file "C:ProgramDataBOINCslots4boinc_bfaf948f1cde7377boinc_bfaf948f1cde7377.vbox" with version "1.16-windows"
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
42:57:17.924605 Saving settings file "C:Userspeter.VirtualBoxVirtualBox.xml" with version "1.12-windows"

VM Execution Log:


VM Startup Log:


VM Trace Log:

ot taken. UUID: 52020d21-b50e-4893-9c5a-5d0b0070538b

2022-01-09 19:41:01 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 19:41:01 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_34178 (UUID: 1c97738e-7c43-4f26-b635-b09c66c0890d)
Name: boinc_34778 (UUID: 52020d21-b50e-4893-9c5a-5d0b0070538b) *

2022-01-09 19:41:02 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "1c97738e-7c43-4f26-b635-b09c66c0890d"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_34178' (1c97738e-7c43-4f26-b635-b09c66c0890d)

2022-01-09 19:51:00 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" pause
Exit Code: 0
Output:

2022-01-09 19:51:01 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" take boinc_35379
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 2150ec43-d0ae-4211-81c8-6da314d76bb1

2022-01-09 19:51:02 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 19:51:02 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_34778 (UUID: 52020d21-b50e-4893-9c5a-5d0b0070538b)
Name: boinc_35379 (UUID: 2150ec43-d0ae-4211-81c8-6da314d76bb1) *

2022-01-09 19:51:02 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "52020d21-b50e-4893-9c5a-5d0b0070538b"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_34778' (52020d21-b50e-4893-9c5a-5d0b0070538b)

2022-01-09 20:01:02 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" pause
Exit Code: 0
Output:

2022-01-09 20:01:04 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" take boinc_35979
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 58e18e3b-fab7-4517-87e7-a1dcd7a9a53b

2022-01-09 20:01:04 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 20:01:04 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_35379 (UUID: 2150ec43-d0ae-4211-81c8-6da314d76bb1)
Name: boinc_35979 (UUID: 58e18e3b-fab7-4517-87e7-a1dcd7a9a53b) *

2022-01-09 20:01:05 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "2150ec43-d0ae-4211-81c8-6da314d76bb1"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_35379' (2150ec43-d0ae-4211-81c8-6da314d76bb1)

2022-01-09 20:11:03 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" pause
Exit Code: 0
Output:

2022-01-09 20:11:03 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" take boinc_36580
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 7e75acdf-2b32-4439-b572-3995748fd97d

2022-01-09 20:11:04 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 20:11:04 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_35979 (UUID: 58e18e3b-fab7-4517-87e7-a1dcd7a9a53b)
Name: boinc_36580 (UUID: 7e75acdf-2b32-4439-b572-3995748fd97d) *

2022-01-09 20:11:04 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "58e18e3b-fab7-4517-87e7-a1dcd7a9a53b"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_35979' (58e18e3b-fab7-4517-87e7-a1dcd7a9a53b)

2022-01-09 20:21:04 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" pause
Exit Code: 0
Output:

2022-01-09 20:21:05 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" take boinc_37181
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: ec16c6eb-37e8-4186-934a-55e27a126c18

2022-01-09 20:21:05 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 20:21:05 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_36580 (UUID: 7e75acdf-2b32-4439-b572-3995748fd97d)
Name: boinc_37181 (UUID: ec16c6eb-37e8-4186-934a-55e27a126c18) *

2022-01-09 20:21:05 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "7e75acdf-2b32-4439-b572-3995748fd97d"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_36580' (7e75acdf-2b32-4439-b572-3995748fd97d)

2022-01-09 20:31:05 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" pause
Exit Code: 0
Output:

2022-01-09 20:31:06 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" take boinc_37782
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 966eeeb1-8c28-4a0f-a685-d07dfd5cd2c0

2022-01-09 20:31:06 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 20:31:06 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_37181 (UUID: ec16c6eb-37e8-4186-934a-55e27a126c18)
Name: boinc_37782 (UUID: 966eeeb1-8c28-4a0f-a685-d07dfd5cd2c0) *

2022-01-09 20:31:07 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "ec16c6eb-37e8-4186-934a-55e27a126c18"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_37181' (ec16c6eb-37e8-4186-934a-55e27a126c18)

2022-01-09 20:37:40 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" cpuexecutioncap 100
Exit Code: 0
Output:

2022-01-09 20:41:06 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" pause
Exit Code: 0
Output:

2022-01-09 20:41:07 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" take boinc_38382
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 83d0a336-4d8d-4153-ad94-e660ba7023b9

2022-01-09 20:41:07 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" resume
Exit Code: 0
Output:

2022-01-09 20:41:07 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_37782 (UUID: 966eeeb1-8c28-4a0f-a685-d07dfd5cd2c0)
Name: boinc_38382 (UUID: 83d0a336-4d8d-4153-ad94-e660ba7023b9) *

2022-01-09 20:41:08 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "966eeeb1-8c28-4a0f-a685-d07dfd5cd2c0"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_37782' (966eeeb1-8c28-4a0f-a685-d07dfd5cd2c0)

2022-01-09 20:50:48 (9148):
Command: VBoxManage -q controlvm "boinc_bfaf948f1cde7377" poweroff
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

2022-01-09 20:50:48 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" list
Exit Code: 0
Output:
Name: boinc_38382 (UUID: 83d0a336-4d8d-4153-ad94-e660ba7023b9) *

2022-01-09 20:50:49 (9148):
Command: VBoxManage -q snapshot "boinc_bfaf948f1cde7377" delete "83d0a336-4d8d-4153-ad94-e660ba7023b9"
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting snapshot 'boinc_38382' (83d0a336-4d8d-4153-ad94-e660ba7023b9)

2022-01-09 20:50:49 (9148):
Command: VBoxManage -q bandwidthctl "boinc_bfaf948f1cde7377" remove "boinc_bfaf948f1cde7377_net"
Exit Code: 0
Output:

2022-01-09 20:50:49 (9148):
Command: VBoxManage -q unregistervm "boinc_bfaf948f1cde7377" --delete
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

20:50:59 (9148): called boinc_finish(194)

</stderr_txt>
]]>
ID: 104101 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5691
Credit: 5,859,226
RAC: 0
Message 104102 - Posted: 9 Jan 2022, 23:08:59 UTC - in response to Message 104101.  

The 0x80070005 error code arises when the Windows access is denied. ... The 0x80070005 error relates to access permissions in Windows, sometimes encountered by users when they are trying to update their Windows or installing a new program, and they don't possess full access permission for certain files

Which is odd, because it ran ok, but when its writing the output there is where the errors are.
I have to get to bed again, but maybe tomorrow night I can look.

But it appears to be a windows permissions thing at first glance.
I see this in a TACC post and a LHC post.

If you search the gibberish:

1) aRC=E_ACCESSDENIED (0x80070005)
2) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}

You might find the answer...add the word BOINC if you can not find what you are looking for.
ID: 104102 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Ed Machak

Send message
Joined: 10 Nov 16
Posts: 7
Credit: 17,339,411
RAC: 0
Message 104103 - Posted: 9 Jan 2022, 23:48:59 UTC - in response to Message 104102.  

Hello,

I apologize for posting off topic but have run out of options. How do I post a new topic"? I've searched the web and these forums for weeks with no luck.

I have a Rosetta login and use it.
Ed Machak
Log out

This is the best advise I found,

"On the Discussions List tab, click New Topic on the drop-down menu
In the Forum drop-down list, select the forum in which you want to create the topic, or create a new forum by clicking the New Forum link.
Enter a Title for the topic.
Enter a Description"

There's no "New Topic" or "New Topic Link" on a forum screen

Beat me up if you must but please help. I'm missing something! Private message response preferred.

Thank you,

Ed Machak
ID: 104103 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 1233
Credit: 14,338,560
RAC: 2,456
Message 104104 - Posted: 10 Jan 2022, 0:03:40 UTC

Some of the forums allow you to start a thread, and some don't. Those that don't, don't have a link for starting a thread, except for the few users allowed to start threads there.

Also, the forums list have a tree structure. Only those at the tips of the trees can allow posting.

Generally, you have to complete a few tasks correctly before you are allowed to post. Some BOINC projects have a forum for users who are having trouble getting started, and may allow posting to these forums with no tasks completed. Such forums often have a moderator who must approve your post before anyone else sees it.
ID: 104104 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mr P Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 1600
Credit: 12,116,986
RAC: 12,028
Message 104105 - Posted: 10 Jan 2022, 0:18:11 UTC - in response to Message 104102.  

The 0x80070005 error code arises when the Windows access is denied. ... The 0x80070005 error relates to access permissions in Windows, sometimes encountered by users when they are trying to update their Windows or installing a new program, and they don't possess full access permission for certain files

Which is odd, because it ran ok, but when its writing the output there is where the errors are.
I have to get to bed again, but maybe tomorrow night I can look.

But it appears to be a windows permissions thing at first glance.
I see this in a TACC post and a LHC post.

If you search the gibberish:

1) aRC=E_ACCESSDENIED (0x80070005)
2) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={The object functionality is limited}

You might find the answer...add the word BOINC if you can not find what you are looking for.


I'm off to bed, but will have a look tomorrow afternoon. The only thing I found was Vbox was not installed with admin rights. Apparently being a user with admin rights isn't good enough. I'll try reinstalling it on an offending machine tomorrow using elevated privileges. Stupid Microsoft.....
ID: 104105 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
.clair.

Send message
Joined: 2 Jan 07
Posts: 274
Credit: 26,399,595
RAC: 0
Message 104106 - Posted: 10 Jan 2022, 1:08:32 UTC

You are not alone with that error, I have some like that, many do run ok , this was another dud.
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
Run time 12 hours 15 min 28 sec
CPU time 3 min 40 sec
It may still be visible by the time you read this - Received 9 Jan 2022, 19:01:27 UTC
It was one of snail workunits that start but get nowhere fast
https://boinc.bakerlab.org/rosetta/result.php?resultid=1463638243
ID: 104106 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Michael E.@ team Carl Sagan

Send message
Joined: 5 Apr 08
Posts: 16
Credit: 1,947,553
RAC: 256
Message 104107 - Posted: 10 Jan 2022, 1:52:09 UTC

Not sure where to post this, but here goes. This is about usability more than technical stuff.

I read the FAQ and see no mention of "virtual box".

I did not see a place that described the different types of Rosetta subprojects and their requirements (memory, CPU, GPU). In fact, Rosetta@home Preferences does not let you choose subprojects.

How are prospective new users gonna find this stuff out?

I am a long-time BOINC user and Rosetta/Ralph member, but do not have time to get lost in the weeds. I installed Virtual Box on my own PC but prefer to not complicate my spouse's desktop system.
ID: 104107 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Jim1348

Send message
Joined: 19 Jan 06
Posts: 881
Credit: 52,257,545
RAC: 0
Message 104108 - Posted: 10 Jan 2022, 3:09:05 UTC - in response to Message 104107.  

How are prospective new users gonna find this stuff out?

That is a very good question. We long-time users have heard about it on the forums, and see the one marked "vbox64" in the applications.
https://boinc.bakerlab.org/rosetta/apps.php

But that is scant information indeed, and tells you nothing about system requirements.
It is a poor way to run a railroad. They won't get much work done that way.
ID: 104108 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
rkv_2401

Send message
Joined: 11 Dec 19
Posts: 5
Credit: 1,232,418
RAC: 0
Message 104109 - Posted: 10 Jan 2022, 3:44:52 UTC - in response to Message 104108.  

I have been trying to run Rosetta@home on 3 different computers for at least the last 3 months now - didn't get a single task no matter what I tried until yesterday, now I've finally had a 'breakthrough' on one of my PCs getting some tasks, but all of them just fail immediately!

Nov 2021 - I try to run Rosetta@home on my Surface Pro 2 (Win 10, i5-4300U w/ 8GB RAM, CPU supports hardware virtualization, virtualization support enabled according to task manager) - 'VirtualBox requires hardware support - which your CPU does not provide' error, or something to that effect. I try restarting the system, reinstalling VBox 6.x, uninstalling Vbox 6.x and installing Vbox 5.2.44 according to some suggestions on this thread, nothing works, I wait for regular tasks, nothing happens, I eventually gave up on it.

Dec 2021 - I try to run Rosetta@home on a new desktop (Win 11, i5-10400 w/ 32GB RAM, CPU supports hardware virtualization, virtualization support enabled according to task manager) - same error as above, tried the same steps, nothing happens, I let it wait for tasks - so far, it hasn't gotten a single one in 14+ days.

Jan 2022 - I half-heartedly try to run Rosetta on my previous crunching machine (Win 10, Ryzen 5 3600 w/ 24GB RAM, CPU supports hardware virtualization, virtualization support DISABLED according to task manager, Hyper-V enabled) - now I start getting tasks on this machine (but not on the 10th gen i5 one that's also plugged in and running BOINC?) And all of them fail anyway - v4.20, vBox 1.03 jobs, all of them fail instantly. *shrugs*

All 3 machines are/were on VBox 5.2.44 as suggested earlier in this thread.
ID: 104109 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
rkv_2401

Send message
Joined: 11 Dec 19
Posts: 5
Credit: 1,232,418
RAC: 0
Message 104110 - Posted: 10 Jan 2022, 3:48:53 UTC - in response to Message 104109.  

Oh, I sometimes clean up my 'computers' list on the R@h page when I reinstall an OS or if something just looks out of place, so that may look a little funky. But I think they should be okay this time.
ID: 104110 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5691
Credit: 5,859,226
RAC: 0
Message 104113 - Posted: 10 Jan 2022, 7:01:32 UTC - in response to Message 104106.  

You are not alone with that error, I have some like that, many do run ok , this was another dud.
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
184:11:40.953516 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5047460a-265d-4538-b23e-ddba5fb84976} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0
Run time 12 hours 15 min 28 sec
CPU time 3 min 40 sec
It may still be visible by the time you read this - Received 9 Jan 2022, 19:01:27 UTC
It was one of snail workunits that start but get nowhere fast
https://boinc.bakerlab.org/rosetta/result.php?resultid=1463638243




Two of you with identical errors. That sounds like a code problem by the team not your machines.
And 12 hrs for 3 minutes of CPU time, definitely something wrong.
Are you running RAH on a dedicated core and don't have much of a system load?
I've run stuff almost like that in the past, but never 12hrs for 3 minutes!
ID: 104113 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5691
Credit: 5,859,226
RAC: 0
Message 104114 - Posted: 10 Jan 2022, 7:04:11 UTC - in response to Message 104109.  

I have been trying to run Rosetta@home on 3 different computers for at least the last 3 months now - didn't get a single task no matter what I tried until yesterday, now I've finally had a 'breakthrough' on one of my PCs getting some tasks, but all of them just fail immediately!

Nov 2021 - I try to run Rosetta@home on my Surface Pro 2 (Win 10, i5-4300U w/ 8GB RAM, CPU supports hardware virtualization, virtualization support enabled according to task manager) - 'VirtualBox requires hardware support - which your CPU does not provide' error, or something to that effect. I try restarting the system, reinstalling VBox 6.x, uninstalling Vbox 6.x and installing Vbox 5.2.44 according to some suggestions on this thread, nothing works, I wait for regular tasks, nothing happens, I eventually gave up on it.

Dec 2021 - I try to run Rosetta@home on a new desktop (Win 11, i5-10400 w/ 32GB RAM, CPU supports hardware virtualization, virtualization support enabled according to task manager) - same error as above, tried the same steps, nothing happens, I let it wait for tasks - so far, it hasn't gotten a single one in 14+ days.

Jan 2022 - I half-heartedly try to run Rosetta on my previous crunching machine (Win 10, Ryzen 5 3600 w/ 24GB RAM, CPU supports hardware virtualization, virtualization support DISABLED according to task manager, Hyper-V enabled) - now I start getting tasks on this machine (but not on the 10th gen i5 one that's also plugged in and running BOINC?) And all of them fail anyway - v4.20, vBox 1.03 jobs, all of them fail instantly. *shrugs*

All 3 machines are/were on VBox 5.2.44 as suggested earlier in this thread.



Well regular 4.2 work is far a few between.
You have virtualization enabled on your CPU's?
You can run 6.x of Vbox here. I am doing it.

Can you post some of your error messages?
It won't be for 12 hours before I can look and research.
ID: 104114 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
rkv_2401

Send message
Joined: 11 Dec 19
Posts: 5
Credit: 1,232,418
RAC: 0
Message 104125 - Posted: 10 Jan 2022, 11:57:01 UTC - in response to Message 104114.  

Hi, yes, I would like to get it working on my i5 machine and the error I keep getting is 'VirtualBox jobs require hardware acceleration support - your processor does not support the required instruction set.'

The machine in question is an i5 10400 on a GIGABYTE B460M-DS3h V2.0, 32GB RAM, 512GB nVME SSD, Windows 11 64-bit. Virtualization is enabled in the BIOS, supported by the hardware, and Windows reports it as being on too.

I would be happy to run memory intensive python tasks on this machine - if they worked!
ID: 104125 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
tullio

Send message
Joined: 10 May 20
Posts: 63
Credit: 630,125
RAC: 0
Message 104127 - Posted: 10 Jan 2022, 13:40:02 UTC

I have an Intel i5 9400F, Windows 11 home edition, VBox 6.1.30 and it works perfectly on rosetta python.
Tullio
ID: 104127 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mr P Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 1600
Credit: 12,116,986
RAC: 12,028
Message 104139 - Posted: 10 Jan 2022, 14:58:31 UTC - in response to Message 104109.  

I have been trying to run Rosetta@home on 3 different computers for at least the last 3 months now - didn't get a single task no matter what I tried until yesterday, now I've finally had a 'breakthrough' on one of my PCs getting some tasks, but all of them just fail immediately!

Nov 2021 - I try to run Rosetta@home on my Surface Pro 2 (Win 10, i5-4300U w/ 8GB RAM, CPU supports hardware virtualization, virtualization support enabled according to task manager) - 'VirtualBox requires hardware support - which your CPU does not provide' error, or something to that effect. I try restarting the system, reinstalling VBox 6.x, uninstalling Vbox 6.x and installing Vbox 5.2.44 according to some suggestions on this thread, nothing works, I wait for regular tasks, nothing happens, I eventually gave up on it.

Dec 2021 - I try to run Rosetta@home on a new desktop (Win 11, i5-10400 w/ 32GB RAM, CPU supports hardware virtualization, virtualization support enabled according to task manager) - same error as above, tried the same steps, nothing happens, I let it wait for tasks - so far, it hasn't gotten a single one in 14+ days.

Jan 2022 - I half-heartedly try to run Rosetta on my previous crunching machine (Win 10, Ryzen 5 3600 w/ 24GB RAM, CPU supports hardware virtualization, virtualization support DISABLED according to task manager, Hyper-V enabled) - now I start getting tasks on this machine (but not on the 10th gen i5 one that's also plugged in and running BOINC?) And all of them fail anyway - v4.20, vBox 1.03 jobs, all of them fail instantly. *shrugs*

All 3 machines are/were on VBox 5.2.44 as suggested earlier in this thread.
Are you sure virtualization is on? Check in the BIOS, don't believe the task manager, maybe it's talking about software virtualization.
ID: 104139 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mr P Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 1600
Credit: 12,116,986
RAC: 12,028
Message 104140 - Posted: 10 Jan 2022, 14:59:38 UTC - in response to Message 104113.  

Two of you with identical errors. That sounds like a code problem by the team not your machines.
And 12 hrs for 3 minutes of CPU time, definitely something wrong.
Are you running RAH on a dedicated core and don't have much of a system load?
I've run stuff almost like that in the past, but never 12hrs for 3 minutes!
In my case loads of RAM, tried to run one at a time, nothing overloaded. If this is a programming error, can we report it somewhere? I doubt any of them are reading this.
ID: 104140 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mr P Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 1600
Credit: 12,116,986
RAC: 12,028
Message 104141 - Posted: 10 Jan 2022, 15:22:46 UTC - in response to Message 104095.  
Last modified: 10 Jan 2022, 15:24:35 UTC

I am getting identical times for running time and CPU time.
Tullio
I'm getting slightly more for CPU time than running time, I thought maybe it was multicore! E.g. 3h31m CPU time in 3h15m running time.

Only seeing this in Boinctasks though, Boinc Manager doesn't seem to show CPU time.
ID: 104141 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5691
Credit: 5,859,226
RAC: 0
Message 104145 - Posted: 10 Jan 2022, 17:10:02 UTC - in response to Message 104140.  
Last modified: 10 Jan 2022, 17:19:25 UTC

Two of you with identical errors. That sounds like a code problem by the team not your machines.
And 12 hrs for 3 minutes of CPU time, definitely something wrong.
Are you running RAH on a dedicated core and don't have much of a system load?
I've run stuff almost like that in the past, but never 12hrs for 3 minutes!
In my case loads of RAM, tried to run one at a time, nothing overloaded. If this is a programming error, can we report it somewhere? I doubt any of them are reading this.
<-- yep. no one reads no one cares.

The only way they notice anything is when the results of 30+ tasks error out and skew the data then they come back for a look. But a few here and there on single machines...nah..not interested.

And I have no way to look at any of your tasks on any of your machines.
It's all 0's and your first machine has not made "contact" since Jan 1.
Everything else is november or even may.
So if they are connected to GRC, then I guess we don't see them.
Which computer ID do you refer to when having problems?
ID: 104145 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5691
Credit: 5,859,226
RAC: 0
Message 104146 - Posted: 10 Jan 2022, 17:10:58 UTC - in response to Message 104141.  
Last modified: 10 Jan 2022, 17:16:45 UTC

I am getting identical times for running time and CPU time.
Tullio
I'm getting slightly more for CPU time than running time, I thought maybe it was multicore! E.g. 3h31m CPU time in 3h15m running time.

Only seeing this in Boinctasks though, Boinc Manager doesn't seem to show CPU time.


It takes a bit to open a VM and check everything and then write everything and shut it down.
Your within the limits. I see about the same.

Run time 4 hours 49 min 55 sec
CPU time 4 hours 38 min 16 sec
Validate state Valid
Credit 218.04
Device peak FLOPS 5.41 GFLOPS
Application version rosetta python projects v1.03 (vbox64)
windows_x86_64
Peak working set size 61.11 MB
Peak swap size 58.45 MB
Peak disk usage 8,745.88 MB


You can find this at the top of the results page for whatever task you want to look at.
ID: 104146 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 . . . 153 · 154 · 155 · 156 · 157 · 158 · 159 . . . 309 · Next

Message boards : Number crunching : Problems and Technical Issues with Rosetta@home



©2024 University of Washington
https://www.bakerlab.org