Thank you. I have changed the settings. I am not sure what you mean by "They're not too bad if you have AVX."

The more recent CPUs have the AVX group of instructions needed to run the Python tasks correctly. Many of the older CPUs don't.

I can't remember where we spoke about this, but it's been said we need to be specific about the disk space available to Boinc.
Instead of leaving the field against "Use no more than xxGb" blank under the Disk & Memory tab of Computing preferences, we should set something large like 500Gb

It's also been said that, on the occasions when we see repeated Computation errors, the Boinc Manager should be closed and "Stop running tasks when exiting the Boinc Manager" should be selected, then search for the file "AIMNet_vm_v2.vdi" in the ProgramData folder and delete it, before restarting Boinc Manager so that a new AIMNet_vm_v2.vdi is certain to be downloaded. Then things tend to start up and run ok.

That's what I've been doing repeatedly.

But recently I've been getting messages that 500Gb isn't sufficient disk space and I need to add more, which I've done several times until I got up to 660Gb, which isn't far off my limit.

So this morning I found lots of Computation errors and went through the routine above.
Except, when I searched for and found the AIMNet_vm_v2.vdi file I opened the file location and finally noticed loads of .tmp files.
AIMNet_vm_v2.vdi comes down as a 2Gb download, and I think as a zip file, but these .tmp files were 7.285Gb in size. I'm guessing they're temporary unzipped copies of AIMNet_vm_v2.vdi left over from previous crashes.

I took a chance, selected and deleted all the .tmp files. They totalled 551Gb and had dates going back to February. A lot of disk space used.
I half-expected a crash or other error once I downloaded a fresh AIMNet_vm_v2.vdi file and then followed up by downloading 26 tasks, but I've had no errors or crashes and I've now been running 10 tasks for 20 minutes, seemingly successfully.

I pass this on for whatever benefit you may find in it

---

Rosetta will not download/run any work items.
I'm running Win10 have reinstalled BOINC with Virtual Box, reset the project with the same result, no work ....

What am I missing?
thx

---

Sid, don't you use a disk cleaner? I have never had your issue.
The disk space thing, yeah we know that now after investigating what happens when you do 0.
(logic error between the programmers and the users)
I always suspend-shutdown client-exit at the end of my crunching day.

Rosetta will not download/run any work items.
I'm running Win10 have reinstalled BOINC with Virtual Box, reset the project with the same result, no work ....

What am I missing?
thx

Because you have to many errors with the python tasks.
Part of the error message is: Sandbox Configuration Enabled
Which makes me think you are not allowing virtualization or a program like Vbox to run as part of your securtiy setup.

I might be wrong....but look up the sandbox thing and see if you can make sense of it related to your system.


One thing is for sure, Vbox is not being allowed to run.
Fix that issue and then go in the details section about your computer on your profile and click on that red button again to get Python tasks again.

Sid, don't you use a disk cleaner? I have never had your issue.
The disk space thing, yeah we know that now after investigating what happens when you do 0.
(logic error between the programmers and the users)
I always suspend-shutdown client-exit at the end of my crunching day.

The ProgramData folder is on my C drive - an SSD. I don't routinely use a disk cleaner, no, and I wouldn't normally mess around within a directory on C
On the disk space thing, the settings we knew, but I haven't heard anyone say their drive has exceeded 500Gb, let alone that it's made up of .tmp files.
That's the news I'm providing so other people can check if they have the same issue and solve it in the simple way I have without repercussions

---

Sid, don't you use a disk cleaner? I have never had your issue.
The disk space thing, yeah we know that now after investigating what happens when you do 0.
(logic error between the programmers and the users)
I always suspend-shutdown client-exit at the end of my crunching day.

The ProgramData folder is on my C drive - an SSD. I don't routinely use a disk cleaner, no, and I wouldn't normally mess around within a directory on C
On the disk space thing, the settings we knew, but I haven't heard anyone say their drive has exceeded 500Gb, let alone that it's made up of .tmp files.
That's the news I'm providing so other people can check if they have the same issue and solve it in the simple way I have without repercussions

I get that...your case is really odd.
I have a 450 dedicated data drive of that with all the projects I used I am only using 38.6.
And its weird you have so many .tmp files. I thought BOINC deleted all files once the data was uploaded and reported?

There appear to be some Python tasks that try to reserve about 19 GB of disk space,

Rosetta@home: Notice from server
rosetta python projects needs 5439.45MB more disk space. You currently have 13634.04 MB available and it needs 19073.49 MB.
4/22/2022 9:08:37 AM

I haven't seen anything yet on whether they do anything useful with that much disk space.

There appear to be some Python tasks that try to reserve about 19 GB of disk space,

Rosetta@home: Notice from server
rosetta python projects needs 5439.45MB more disk space. You currently have 13634.04 MB available and it needs 19073.49 MB.
4/22/2022 9:08:37 AM

I haven't seen anything yet on whether they do anything useful with that much disk space.

That is the same kind of message I was getting and so I started a thread about it
https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14903

For some reason vm hard drive image is 6.94 gb in size.
three tasks use 20.82 gb.
You can enable ntfs compression on slots directory to reduce files size to 2.86 gb.

Sid, don't you use a disk cleaner? I have never had your issue.
The disk space thing, yeah we know that now after investigating what happens when you do 0.
(logic error between the programmers and the users)
I always suspend-shutdown client-exit at the end of my crunching day.

The ProgramData folder is on my C drive - an SSD. I don't routinely use a disk cleaner, no, and I wouldn't normally mess around within a directory on C
On the disk space thing, the settings we knew, but I haven't heard anyone say their drive has exceeded 500Gb, let alone that it's made up of .tmp files.
That's the news I'm providing so other people can check if they have the same issue and solve it in the simple way I have without repercussions

I get that...your case is really odd.
I have a 450 dedicated data drive of that with all the projects I used I am only using 38.6.
And it's weird you have so many .tmp files. I thought BOINC deleted all files once the data was uploaded and reported?

It is odd - I have no explanation or any idea what circumstances created it.
I only have this observation, for whatever value anyone else can find in it.
People might want to examine their own ProgramData folder and pre-empt the events that affected me if they see the same thing.
We're all in self-help mode

---

And it's weird you have so many .tmp files. I thought BOINC deleted all files once the data was uploaded and reported?

It is odd - I have no explanation or any idea what circumstances created it.
I only have this observation, for whatever value anyone else can find in it.
People might want to examine their own ProgramData folder and pre-empt the events that affected me if they see the same thing.
We're all in self-help mode

It TRIES to delete all files once the data was uploaded and reported. However, improperly shutting it down can prevent this from happening,

I use a disk cleaner on an SSD. It only looks for files it can delete.

https://www.google.com/search?client=firefox-b-1-d&q=disk+cleanup+windows+10

It should delete any temporary files that BOINC left on place when it was improperly shut down, such as having the power turned off without first telling BOINC to suspend and exit.

I only allow it to delete types of files that I agree are no longer useful.

Sid, don't you use a disk cleaner? I have never had your issue.
The disk space thing, yeah we know that now after investigating what happens when you do 0.
(logic error between the programmers and the users)
I always suspend-shutdown client-exit at the end of my crunching day.

The ProgramData folder is on my C drive - an SSD. I don't routinely use a disk cleaner, no, and I wouldn't normally mess around within a directory on C
On the disk space thing, the settings we knew, but I haven't heard anyone say their drive has exceeded 500Gb, let alone that it's made up of .tmp files.
That's the news I'm providing so other people can check if they have the same issue and solve it in the simple way I have without repercussions

I get that...your case is really odd.
I have a 450 dedicated data drive of that with all the projects I used I am only using 38.6.
And it's weird you have so many .tmp files. I thought BOINC deleted all files once the data was uploaded and reported?

It is odd - I have no explanation or any idea what circumstances created it.
I only have this observation, for whatever value anyone else can find in it.
People might want to examine their own ProgramData folder and pre-empt the events that affected me if they see the same thing.
We're all in self-help mode

After that 0 value error thing and before the guys at github figured it out, I dropped some cash on a new SDD to put the data on. You might consider that if your budget allows it. Then you split program files to c: and data to d: (or whatever). Then data can have all the space it needs and only BOINC program files reside on c:

On my c: I have only 91 free from 220 (only boinc program files are here) but on d: I have 419 out of 450 freeand the data from 6 projects uses only 15.2. Rosetta is 8.63 of this total. 5,357 files and 424 folders.

You might not need 450GB and maybe something like a 250GB drive would work and just move data to there, then no matter what it wants, there is always lots of room. It's and idea, not sure if your bank account would like that idea or not.

I'm encountering a new problem, has anyone else see it?. I have three Python tasks in the state "Postponed: VM Hypervisor failed to enter an online state in a timely fashion."

I'm running BOINC 7.6.20 and was on VirtualBox 6.1.32 - combination had been working generally happy, and I haven't changed any BOINC settings recently (or had any significant changes to available disk space). I've updated VBox to 6.1.34 to see if that resolves it, but it looks like the Python tasks are being postponed for a day and none of the others have started.

Can you unupdate to 5.2.44?

And it's weird you have so many .tmp files. I thought BOINC deleted all files once the data was uploaded and reported?

It is odd - I have no explanation or any idea what circumstances created it.
I only have this observation, for whatever value anyone else can find in it.
People might want to examine their own ProgramData folder and pre-empt the events that affected me if they see the same thing.
We're all in self-help mode

It TRIES to delete all files once the data was uploaded and reported. However, improperly shutting it down can prevent this from happening,

I use a disk cleaner on an SSD. It only looks for files it can delete.

https://www.google.com/search?client=firefox-b-1-d&q=disk+cleanup+windows+10

It should delete any temporary files that BOINC left on place when it was improperly shut down, such as having the power turned off without first telling BOINC to suspend and exit.

I only allow it to delete types of files that I agree are no longer useful.

Ok, I've just used Windows Disk cleanup and ensured storage sense is enabled and freed up a few Gb, but that's on a PC that isn't running VBox
I'll give that a go when I get back to my main PC tomorrow evening

---

Can you unupdate to 5.2.44?

I'll give that a try if there are continued problems. I just went back and looked, the existing tasks are still postponed (1 day hasn't elapsed yet, and there isn't an obvious way to manually resume them), but one of the other python tasks seems to be running ok so maybe it was just a transient issue.

Update: The first task to be postponed reached the end of its one day postponement, and now appears to be computing successfully (in VBox 6.1.34). Haven't tried reverting to previous version to see what happens, but whatever the problem was it seems to have resolved.

Can you unupdate to 5.2.44?

I'll give that a try if there are continued problems. I just went back and looked, the existing tasks are still postponed (1 day hasn't elapsed yet, and there isn't an obvious way to manually resume them), but one of the other python tasks seems to be running ok so maybe it was just a transient issue.

I've found a way to manually resume such tasks. Suspend all tasks, then exit BOINC. I've forgotten if it's necessary to restart Windows at this point. Then restart BOINC and tell it to resume tasks.
,

Ok, I've just used Windows Disk cleanup and ensured storage sense is enabled and freed up a few Gb, but that's on a PC that isn't running VBox
I'll give that a go when I get back to my main PC tomorrow evening

I run the Windows disk cleanup (including system files) then run treesize which shows me what folders are using the most, so I can manually remove stuff I don't want anymore. Last time I reduced the stuff on my disk by a third.

I only bother doing this when the line changes from blue to red in windows explorer.