There is this 1600x1200 Eizo FlexScan
https://www.amazon.com/Eizo-FlexScan-S2133-BK-Monitor-1600x1200/dp/B00KDMMKD0

There is this 1600x1200 Eizo FlexScan
https://www.amazon.com/Eizo-FlexScan-S2133-BK-Monitor-1600x1200/dp/B00KDMMKD0

A thousand dollars for a 21" screen? What planet do you come from? I have a 20" 4:3 here at that resolution I bought for $60.

I don't know what the problem is, the rosetta units advance in calculation but the load of the cpus remains at zero... as if nothing was calculated...

Tested with Boinc Windows 7.16.20 (x64) with or without VM.

A solution ?

Thanks in advance for the reply.

---

I think you can open virtualbox manager gui and show vm screens and if vm is stuck you can try to reset vm.

I have a Rosetta Python task with a problem I've never seen before.

It's been running (or claiming to be) for hours, but it's still showing no CPU time and no memory used so far.


Application rosetta python projects 1.03 (vbox64)
Name aaam-PHE_pp-mNMVAL-ACPC-AMACBEN2_2_2554686_6
State Running
Received 6/4/2022 6:13:14 PM
Report deadline 6/7/2022 6:13:13 PM
Estimated computation size 80,000 GFLOPs
CPU time ---
CPU time since checkpoint ---
Elapsed time ---
Estimated time remaining 08:00:00
Fraction done 0.000%
Virtual memory size 0 bytes
Working set size 0 bytes
Directory slots/6
Executable vboxwrapper_26203_windows_x86_64.exe


I've decided to let it reach its deadline, then abort it.

I've never checked the memory, but no CPU time is the common bug everyone is getting, just send it back and get on with another. It's not going to be of any use sitting there not using the CPU, you're just wasting a core.

Hey, we're actually nearing the end of the pythons! Hopefully either the next batch will work better, or preferably they won't use VB anymore.

no CPU time is the common bug everyone is getting

Correct.
As soon as you see it happening, don't wait for something to change - it never EVER does.
Abort it on sight every time

---

no CPU time is the common bug everyone is getting

Correct.
As soon as you see it happening, don't wait for something to change - it never EVER does.
Abort it on sight every time

Sounds like an instruction to a soldier.

one of the `fun` things about the Linux command line is the `kill` command
A great way to deal will zombie processes
and rosetta workunits .

You mean exactly like pressing "end task" in Windows Task Manager?

And wouldn't you be better letting Boinc kill it? Then it knows to start another one.

I did an experiment with one of these tasks that seem to never finish. I let it run. Elapsed time is now 4 days 5:12:xx hours with 00:00:01 seconds remaining. I am curious if it will ever finish and was curious about what the credits might look like, but the task took too long.

The Rosetta BOINC status says the task has: "timed out - no response". Task id is: aagb-FPS_pp-mNMPHE-mACPenC13T-B3LEU_pp_3_2601503_6_0

As Sid says, if the time needed for a "Rosetta python projects 1.03 (vbox64)" is much more than is expected, stop the task.

Ah, this is the problem. The Python book has only one use:

It's a pity, the new version of Python seems great

---

You mean exactly like pressing "end task" in Windows Task Manager?
And wouldn't you be better letting Boinc kill it? Then it knows to start another one.

Yes , true , and it iz wot I do , Just commenting and being a silly bint .

Ah, this is the problem. The Python book has only one use:

It's a pity, the new version of Python seems great

PyPy ROTFPMSL! Is that the one for kids?

You mean exactly like pressing "end task" in Windows Task Manager?
And wouldn't you be better letting Boinc kill it? Then it knows to start another one.

Yes , true , and it iz wot I do , Just commenting and being a silly bint .

You sound like a fun bint, what are you wearing? ;-)

You mean exactly like pressing "end task" in Windows Task Manager?
And wouldn't you be better letting Boinc kill it? Then it knows to start another one.

Yes , true , and it iz wot I do , Just commenting and being a silly bint .

You sound like a fun bint, what are you wearing? ;-)

At the moment I am not wearing my one piece `avatar` na`vi suit , with tail , though the hair is real ,
I never was as good looking as Neytiri , or blue ;-)

You mean exactly like pressing "end task" in Windows Task Manager?
And wouldn't you be better letting Boinc kill it? Then it knows to start another one.

Yes , true , and it iz wot I do , Just commenting and being a silly bint .

You sound like a fun bint, what are you wearing? ;-)

At the moment I am not wearing my one piece `avatar` na`vi suit

If you're not wearing it then.... oh!

, with tail , though the hair is real ,I never was as good looking as Neytiri , or blue ;-)

I'm not so sure that's a suit. Isn't that just her natural skin?
https://james-camerons-avatar.fandom.com/wiki/Na%27vi

I did an experiment with one of these tasks that seem to never finish. I let it run. Elapsed time is now 4 days 5:12:xx hours with 00:00:01 seconds remaining. I am curious if it will ever finish and was curious about what the credits might look like, but the task took too long.

The Rosetta BOINC status says the task has: "timed out - no response". Task id is: aagb-FPS_pp-mNMPHE-mACPenC13T-B3LEU_pp_3_2601503_6_0

As Sid says, if the time needed for a "Rosetta python projects 1.03 (vbox64)" is much more than is expected, stop the task.

I'm rarely confident of anything regarding computers, but because I work away 2-4 consecutive days every week I routinely come back to one or two tasks in progress for whole days.
With one solitary exception, they show reduced CPU runtimes of 1 or 2hrs down to as little as 20-something seconds. Not one ever restarts once stalled

---

You might be able to leave it running more than the number of cores you have, then if some stall your PC is still flat out while you're away. Not sure if you can do this for tasks designed for a single core, but I do it with multicore Cosmology tasks:

<app_config>
   <app_version>
       <app_name>camb_boinc2docker</app_name>
       <plan_class>vbox64_mt</plan_class>
       <avg_ncpus>5</avg_ncpus>
       <cmdline>--nthreads 6</cmdline>
   </app_version>
</app_config>

This tells the actual app to use 6 cores per task, but the Boinc scheduler they only use 5.

Or perhaps there's another way to tell Boinc you have more cores than you really do?

I just got back from vacation and restarted my system. I didn't check it and today I did and I see this stupid project dropped me from VM jobs until I reset it again a bit ago. This project really enjoys kicking people off its VM stuff.