![]() Boinc Manager uses a simulated progress that it shows for the user but it is wildly inaccurate at best of times and downright bogus sometimes. The task's actual progress is also not reported back to Boinc Manager. Exactly how much I don't know but OpenIFS is quite a high memory app anyway so the relatively small overhead probably won't matter.Ģ. I've not looked in detail at this yet though there is obviously a memory overhead to using a VM. I would have thought the boincmgr would see the memory used by the virtual machine itself which will be very close to the actual task usage. Windows task manager doesn't know the actual memory consumption of the virtual machine either, Task Manager just sees that memory is used but does not know by which process (or at least won't show it to you).The virtual machine will be created with a memory partition big enough for the task's rsc_memory_bound plus an overhead for the minimal OS running in the virtual machine. So actual memory consumption monitoring needs to be done inside the VB. Boinc (or Boinc Manager) that is running in the host OS does not know about the memory usage of an VB task, it relies only to the memory_rsc_bounds value that is set up for a task. I have a few observations from the LHC about running VB tasks:ġ. However, it ran one cpdn task, very slowly. We got the ubuntu VM and BOINC/cpdn running. I suspect it's unhappy with the EFI boot? Any suggestions on fixing this are welcome.ģ. Neither the migrated copy nor a fresh install get beyond starting the shell. ![]() Unfortunately, the new host does not like the Mac Mojave VM. The indicated requirements for upcoming openIFS tasks, says that more physical RAM will likely be needed. ![]() Tick 'Leave non-GPU tasks in memory while suspended'.Įdit: With the VM running 5 cpdn openIFS tasks, Resource Monitor reports 39GB Physical Memory in use and 1.6GB of cache. Set the number of VM cpus to N-1 physical cores. There is no way to reduce the VM disc partition size in VirtualBox without creating a new vdi and moving the VM files around. Oops, fat fingers had added an extra zero. Increasing the 40GB vdi disc size in VirtualBox to 100GB created a 990GB VM disc partition. VirtualBox 6.1 is happily running the migrated ubuntu 20.04.1 VM with BOINC/cpdn. The ubuntu and Mojave VMs were migrated to this host. i7-8700 WIN10 host with 40GB of physical RAM The answer is to pause Windoze updates for as long as you can and manage the WIN10 updates manually.Ģ. The run-time cpdn crash issues were (in part) from Windoze updates unexpectedly rebooting the host. If you need to make a much bigger linux VM disc, try GParted. The on-line tutorials all create a very small VM disc, far too small. In practice, 16GB physical RAM was insufficient. You'll need at least 24GB of physical RAM, peferably 32GB. When sizing the VM memory, the Windoze host will need a minimum of 8GB RAM reserved for Windoze to play in. i7-3770 WIN10 host with 32GB of physical RAM. We've been runing Virtualbox 6.1 with ubuntu 20.04.1 VM for 18 months and Mac Mojave VM for 9 months.ġ. Also, unlike regular Linux installations, WSL2 ones come with all of the 32-bit libraries needed to run Hadley models by default. The quirks don't show up on CPDN, only on the complicated to set up projects like LHC ATLAS and Theory. I have used it extensively for BOINC and while it occasionally has its quirks, it runs very well. It uses a lot less resources than VBox, and you can just close PowerShell and it runs in the background, you don't even see it, unlike VBox. When it comes to Linux virtualization on Windows PCs, I'm a big fan of WSL2, which is part of Windows. The only thing that took care of the issue was disabling time sync in the macOS in the VM, so I just keep it off. I tried a few things but couldn't figure out the problem. One problem I did have, which crashed the models, is time mismatch that BOINC was detecting but the clocks on both the VM and Windows10 matched up. Windows and VBox upgrades didn't break it either. Ran stably for months crunching those models and I devoted and used a lot of resources to that VM. ![]() Could not get it to work on Ryzen 5900X but did get it working on an older Intel, i7-4790, both PCs are Windows 10. My only significant experience with VBox is getting a macOS Mojave VM set up to run those Mac only Hadley models.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |