Are you ever going to release work other than that? Or should I just remove Rosetta from boinc. It's going on 30 days since you last gave me anything to process.

Generally every few days some is released, but it's so little that if you don't request work as it is released then you won't get any.
One a week, or every other week, there have been some larger batches released, but if your system doesn't request work while it is available (a few hours or so), then you naturally won't get any.

---

Grant
Darwin NT

Generally every few days some is released, but it's so little that if you don't request work as it is released then you won't get any.
One a week, or every other week, there have been some larger batches released, but if your system doesn't request work while it is available (a few hours or so), then you naturally won't get any.

What hurts is that my BOINC client seems to check the Rosetta server infrequently. The longer the server makes the client wait, the longer the client waits before trying again. So my client has gone so long since getting the last work units that it now checks only once every 24 hours. There was a batch of work units earlier (now yesterday). As soon as I noticed it, I set all the other projects to get no new work, and than tried to get some of the new work units. But I was too slow and they all were gone before my Linux machine could get any. I have another machine running Windows and it got some of them.

---

Back to VirtualBox.

I installed Leap_15.4 in a VirtualBox, simple enough since the OS I run is Leap_15.4 and I have an iso image handy.

While running in that VirtualBox I used yast to install the boinc client and manager. I added Rosetta using the boinc manager.
It promptly told me "Message from server: VirtualBox is not installed."

Back to VirtualBox.

I installed Leap_15.4 in a VirtualBox, simple enough since the OS I run is Leap_15.4 and I have an iso image handy.

While running in that VirtualBox I used yast to install the boinc client and manager. I added Rosetta using the boinc manager.
It promptly told me "Message from server: VirtualBox is not installed."

Not surprising if you didn't install VirtualBox in the Leap VM that was running under VirtualBox.

---

Grant
Darwin NT

Seems a bit redundant.

Meaning, while running VirtualBox I have to install VirtualBox again. But while running the original process, that I used to install the VirtualBox, and started, it still tells me there's no VirtualBox installed.
So which VirtualBox didn't I run, how many VirtualBox's do I need running?

Seems a bit redundant.

Because of what you are doing.
You are running Virtual Box on a computer- it allows you to run Virtual Machines. You are installing Leap on one of those Virtual Machines. The whole point of VMs is that the OS running on them is completely unaware of everything else other than the VM it is running on. So any software running on that VM will be unaware it is running on a VM & also completely unaware of what the VM is running under.

So, since you have installed Leap under a VM, then you must install Virtual Box on that Leap VM in order to run any software on that Leap VM that requires Virtual Box to run.
Or you could just do what everyone else in the world does, install your choice of OS- which in this case is Leap -on the computer in question. Then install BOINC & Virtual Box on it.


It's only a complicated mess because that is what you are choosing to do.

---

Grant
Darwin NT

Thanks for your assistance.
I guess I'll just forget about running Rosetta, to bad I was sitting at #140 until the virtualbox hit the fan.

FWIW, my computer has boinc installed on it, a virtual machine defined via virtualbox, the virtual machine has boinc on it (and not much else). Nothing will run rosetta. I get the same message that virtualbox isn't installed on both. The computer at the top got jobs, they quit after about 10 seconds with a notation in the log that the output file was absent. The boinc manager said there was a computation error. Not much to work with there.

Thanks for your assistance.
I guess I'll just forget about running Rosetta, to bad I was sitting at #140 until the virtualbox hit the fan.

FWIW, my computer has boinc installed on it, a virtual machine defined via virtualbox, the virtual machine has boinc on it (and not much else). Nothing will run rosetta. I get the same message that virtualbox isn't installed on both. The computer at the top got jobs, they quit after about 10 seconds with a notation in the log that the output file was absent. The boinc manager said there was a computation error. Not much to work with there.

Rather than set up VBox and load Boinc onto it download the version of Boinc that contains VBox and run that.

Which repository has the openSUSE Leap 15.4 version of that software?

Which repository has the openSUSE Leap 15.4 version of that software?

With apologies, I’ve just checked and that method only appears to be available for Windows. My mistake.

Thanks for your assistance.
I guess I'll just forget about running Rosetta, to bad I was sitting at #140 until the virtualbox hit the fan.

FWIW, my computer has boinc installed on it, a virtual machine defined via virtualbox, the virtual machine has boinc on it (and not much else). Nothing will run rosetta. I get the same message that virtualbox isn't installed on both. The computer at the top got jobs, they quit after about 10 seconds with a notation in the log that the output file was absent. The boinc manager said there was a computation error. Not much to work with there.

The stderr output from one of your failed Tasks.

Stderr output
<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 5 (0x5, -251)</message>
<stderr_txt>
2022-07-16 17:17:48 (9662): vboxwrapper (7.7.26197): starting
2022-07-16 17:17:48 (9662): Feature: Checkpoint interval offset (86 seconds)
2022-07-16 17:17:48 (9662): Detected: VirtualBox VboxManage Interface (Version: 6.1.32)
2022-07-16 17:17:48 (9662): Detected: Minimum checkpoint interval (600.000000 seconds)
2022-07-16 17:17:48 (9662): Create VM. (boinc_db8b32991e5b0a4b, slot#32)
2022-07-16 17:17:48 (9662): Setting Memory Size for VM. (6144MB)
2022-07-16 17:17:48 (9662): Setting CPU Count for VM. (1)
2022-07-16 17:17:49 (9662): Setting Chipset Options for VM.
2022-07-16 17:17:49 (9662): Setting Boot Options for VM.
2022-07-16 17:17:49 (9662): Setting Network Configuration for NAT.
2022-07-16 17:17:49 (9662): Disabling VM Network Access.
2022-07-16 17:17:49 (9662): Disabling USB Support for VM.
2022-07-16 17:17:49 (9662): Disabling COM Port Support for VM.
2022-07-16 17:17:49 (9662): Disabling LPT Port Support for VM.
2022-07-16 17:17:49 (9662): Disabling Audio Support for VM.
2022-07-16 17:17:49 (9662): Disabling Clipboard Support for VM.
2022-07-16 17:17:49 (9662): Disabling Drag and Drop Support for VM.
2022-07-16 17:17:49 (9662): Adding storage controller(s) to VM.
2022-07-16 17:17:49 (9662): Adding virtual disk drive to VM. (vm_image.vdi)
2022-07-16 17:17:49 (9662): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB)
2022-07-16 17:17:49 (9662): Enabling shared directory for VM.
2022-07-16 17:17:49 (9662): Starting VM. (boinc_db8b32991e5b0a4b, slot#32)
2022-07-16 17:17:49 (9662): Error in start VM for VM: -2135228411
Command:
VBoxManage -q startvm "boinc_db8b32991e5b0a4b" --type headless
Output:
VBoxManage: error: Could not launch the VM process for the machine 'boinc_db8b32991e5b0a4b' (VERR_ACCESS_DENIED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())" at line 727 of file VBoxManageMisc.cpp

2022-07-16 17:17:49 (9662): VM failed to start.
2022-07-16 17:17:49 (9662): Powering off VM.
2022-07-16 17:17:49 (9662): Deregistering VM. (boinc_db8b32991e5b0a4b, slot#32)
2022-07-16 17:17:49 (9662): Removing network bandwidth throttle group from VM.
2022-07-16 17:17:50 (9662): Removing storage controller(s) from VM.
2022-07-16 17:17:50 (9662): Removing VM from VirtualBox.
2022-07-16 17:17:50 (9662): Removing virtual disk drive from VirtualBox.

Could not launch the VM process for the machine 'boinc_db8b32991e5b0a4b' (VERR_ACCESS_DENIED)

Makes it look like some sort of permission issue.

---

Grant
Darwin NT

Thanks for that output. Is there a way for me to see that on my own? I'd like to try some things but it might take a while to do them all (I have things I need to do out of town that will take me away from here for 2 or 3 days per week). That VM no longer exists and I'd have to modify some things in the existing one (the original was a minimal install with just boinc installed on it, the one now was created so I could play around with xfce vice the kde I'm using now).

Thanks for that output. Is there a way for me to see that on my own?

Yep, it's the output from one of your Tasks.
Click on your name here in the forum, on Computers, click on View.
Click on Tasks for a given computer. On any of the Errored Tasks, click on any Task ID number in the the first column (Task, click for details).

---

Grant
Darwin NT