1) Forums : Technical Support : Issues with vbox when working (Message 22657)
Posted 28 Sep 2020 by icollins99
Post:
Alrighty!! Looks like that XML script did the thing! It does seem to only be running on 6 threads, which is a lot more than 0 for certain, haha. What I found odd is that, like you saw, my preferences were set to 6 CPUs, but each new task was calling for 10! I'll make sure to keep that script in the folder, if only to make sure that it keeps the correct config. Thanks for all your help, this has really been getting my goat for a while now! Well, back to working with a working machine! Anything else that I should make sure is configured correctly before I set it off?
2) Forums : Technical Support : Issues with vbox when working (Message 22655)
Posted 28 Sep 2020 by icollins99
Post:
So, I was able to find the logs spit out by the most recent VM, so hopefully it will be able to reveal something. It did see that there was an error in the settings for the VM, saying that the number of CPUs exceeded the number available (paraphrasing, I forgot to copy the warning) but wouldn't allow me to change the number of CPU's I wanted the VM to use. I did have my settings set to only 6 CPUs through Cosmology@home after I began this thread, so fingers crossed that with new assignments it is able to assign the proper number of cores.

[url]http://www.mediafire.com/file/mz6c3ryet25d55r/boinc_f2f2a25a735bfeb9-2020-09-27-18-18-01.log/file[url]
3) Forums : Technical Support : Issues with vbox when working (Message 22654)
Posted 27 Sep 2020 by icollins99
Post:
Alright, so a few minutes after letting it run, the test failed, stating computational error, closing the VM. When I had last checked it, the estimated arrival was showing 12 days, with it stuck at .1% completion, which I would guess is the lowest number to register. I'll post the properties panel. [img]https://ibb.co/mXtpJQF[img]
4) Forums : Technical Support : Issues with vbox when working (Message 22653)
Posted 27 Sep 2020 by icollins99
Post:
Sorry, my terminology is a bit rusty. I would assume SVM or AMD-V is on, as I am showing virtualization it enabled through task manager. I do not have Microsoft Hyper-V enabled, as far as I know, but I have also never seen the setting. I do have Windows defender core isolation off, although I don't think it would have much to do with my problem. I did see, when I looked up AMD-V, It said something about IOMMU, and how those settings affect GPU pass-through, but I don't know how that would affect me in my case. I have all of my settings changed how you said, and I'm waiting for it to chew through all of my legacy tasks, which thankfully take no time at all, so it can run docker in peace. I checked the settings for the VM, and it lists only 9 CPU cores assigned to it, which is what was listed in the description of the task. The rest of my tasks, which run alongside Cosmology@Home, don't seem to have throttling issues, as they all finish before deadlines.
5) Forums : Technical Support : Issues with vbox when working (Message 22651)
Posted 27 Sep 2020 by icollins99
Post:
My computer hasn't reported work in the past 30 days, so it doesn't show in the first part, but it is listed under "all computers." Checking my computer stats, it does say that hyper-v is enabled, and it is switched on in by BIOS. Looking at VBox, it lists al log the VMs that were created as inaccessible, with the error code -103, path not found, but has listed assigned tasks as working or paused in the past, so I'm guessing that a restart might have killed it. But, even in a situation like this, it seems to always return to normalcy, sans actually working, getting new assignments and opening new VMs without conflict. Here's my computer, hopefully you can see something I don't. https://www.cosmologyathome.org/show_host_detail.php?hostid=427527
6) Forums : Technical Support : Issues with vbox when working (Message 22649)
Posted 26 Sep 2020 by icollins99
Post:
Checked the settings, nothing there that seemed to be limiting it. I had my CPU and resources set to maximum, so I reset everything to unhinged again, to be sure. No luck there, though.
7) Forums : Technical Support : Issues with vbox when working (Message 22648)
Posted 26 Sep 2020 by icollins99
Post:
So, this is going to seem strange, but the tasks that are failing are the camb_boinc2docker tasks. The only ones that seem to be going through are the camb_legacy tasks. Shoulda put that in the post, huh? My CPU isn't too far off from yours, I'm using a Ryzen 3600X for all my tasks. I seemed to be having the same problem wen running tasks from LHC@home, whom also uses virtualization. I will definitely check my settings to see if anything there got bunged up, so fingers crossed!
8) Forums : Technical Support : Issues with vbox when working (Message 22646)
Posted 24 Sep 2020 by icollins99
Post:
Hello!

For a while now, I have had some severe issues with working on any assigned tasks that require vbox. the main issue is that projects get assigned to my machine no problem, but once it reaches .100% progress, it stops all together, still claiming that it is working on the assignment, and continues to count up, with the estimated return time exceeding 10 days. I do have CPU virtualization enabled for my processor, 3600X, and the vbox manager lists each VM as working, and I'm able to access the machine. I have no actual experience with VMs, so any help would be greatly appreciated!