Posts by rkv

1) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 104255) Posted 15 Jan 2022 by rkv_2401 Post: Thanks to everyone who pointed out that virtualization was disabled on my Ryzen 3600 machine. I enabled SVM mode and it has been working for a couple of days now. However, this wasn't an optimal solution for me as I would rather have this computer crunching SiDock/WCG and my 10th gen i5 desktop with 32GB of RAM working on these VBox jobs. In fact, I only enabled SVM mode on the Ryzen desktop because Rosetta kept sending me VBox tasks even after I'd informed them NOT to (with the toggle switch, as I'd posted earlier), and it kept getting WUs that always errored out and clogging up other BOINC projects. I couldn't understand why a machine with virtualization disabled can doggedly keep getting VBox jobs, but an i5 from 2020 supposedly does not have hardware support for virtualization instructions. I checked again on the Intel desktop, Virtualization is enabled in Windows, VT-d enabled in the BIOS. So I investigated further and eventually realized that turning off Hyper-V on the Intel desktop made the error go away. However, this didn't work for the Surface Pro 2 (which I deleted from my list of computers after a month of no credit, it was a duplicate entry anyway) as Hyper-V was already off. Anyway, I will now be devoting the i5 desktop purely to Rosetta@home and the Ryzen to share with other projects. TL;DR - Rosetta@home kept sending me VBox jobs even after being requested not to and annoyed me into finding a solution for my problem :) Error #1 - Virtualization was disabled on Ryzen desktop. Solution - Enabled SVM mode in BIOS, ensured Hyper-V was off. Error #2 - "VirtualBox jobs require hardware acceleration support. Your processor does not support the required instruction set" - on hardware that does support virtualization. (Intel 10th gen i5, 4th gen i5-4300U) Solution that worked for me : Turn off Hyper-V (worked on 10th gen i5, Hyper-V was already off on Surface Pro 2 and I haven't found a solution for it yet.) Other suggestion - the 'tasks' part used to have the last 20 tasks per computer up until some point last year. It was useful to determine the performance, runtime, etc. of a computer compared to another one. Now it disappears very quickly. Makes it difficult to debug why a task would have failed and also makes it harder to track the other parameters I've mentioned earlier.
2) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 104196) Posted 13 Jan 2022 by rkv_2401 Post: Thanks for your efforts to help, Greg. I've decided to just wait it out - because on the machines that I am sure have virtualization enabled (couple of i5s), I get an error saying VirtualBox jobs are not supported by my hardware and got no tasks And on the machine that I'm not sure has virtualization enabled (Ryzen 5 3600), I got a bunch of VBox jobs and Rosetta v4.20 jobs one time where all 11 of them errored out instantly. Rosetta v4.20 jobs are supposed to be free of the virtualization problem, right? All 3 of these machines are working well on WCG and SiDock@home - and I can't take any of them offline right now to restart them and find out what's going wrong, particularly when there's a chance that the tasks I happen to be catching are themselves buggy. I've still configured 2 of them to get Rosetta@home tasks, and I guess I'll set up both of them to avoid VBox jobs as well. Fingers crossed!
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 104125) Posted 10 Jan 2022 by rkv_2401 Post: 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!
4) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 104110) Posted 10 Jan 2022 by rkv_2401 Post: 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.
5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 104109) Posted 10 Jan 2022 by rkv_2401 Post: 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.

Posts by rkv_2401