Opened 7 years ago
Last modified 7 years ago
#16817 new defect
Debugging high CPU usage macOS
| Reported by: | Claytron | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.22 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Mac OS X |
Description
I'm using docksal to run a virtual box on macOS 10.12.4. When I view the activity monitor VBoxheadless is consumming 120-140% CPU. I've tried toggling a few things in the settings, but I'm out of my depth in terms of actually debugging the issue.
Attachments (1)
Change History (3)
by , 7 years ago
| Attachment: | docksal-2017-06-06-10-34-21.log.zip added |
|---|
comment:1 by , 7 years ago
I had to look up "docksal" to see what it actually was; a tool that builds upon Docker, that builds upon VirtualBox. Now, the big question is: do you get that behavior with a standalone version of VirtualBox? Otherwise I'm afraid you have too many layers of "builds upon" which makes troubleshooting really, really hard, because you can't be sure which "layer" is responsible for what you're seeing.
Second, if VirtualBox (or VBoxHeadless) is using the CPU, that most probably means that the guest is using the CPU. Have you checked your guest? 'top' I guess?
Third, have you tried to run the guest "normally", from within VirtualBox Manager? What about that behavior?
comment:2 by , 7 years ago
I forgot to mention that it's usually better and faster, if issues like this one get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
So, if you can, please open a new thread in the VirtualBox on Mac OS X Hosts section of the forums.
Be sure to mention that you came from the bugtracker and include the ticket #.
Log file