I'm not sure why, but VB is a privileged process and BOINC is not and it may be the signal is blocked by Doze security. No matter, when BOINC asks VB to shut, which is does when Doze tells BOINC to die from your shutdown, VB is not killing itself. Every O/S, and VB is a guest O/S on Doze, always has some stay awake tasks.Īs to the active connections issue, while that is IP related I think that is the 127.0.0.1 loopback that is active for inter-process signals and not traffic to outside. LHC Atlas uses up to 8, depending on my settings, but this is displayed in Boinc, Boinc knows how many cores are allocated to that task. The CPU usage went to zero almost immediately.Īlso you will find vitrualbox uses all your cores. When I pause Boinc, the CPU stops completely, I just paused a 24 core machine in Boinc, 6 of the cores running LHC Theory tasks under Vbox. You will also find if you pause BOINC that virtualbox does not pause. Virtualbox wasn't designed to have BOINC control it in such a fashion.
0 kommentar(er)
