Claytron wrote:what is the "guest"?
You sound like a fairly new user to VirtualBox. Since you are expected to know some basic terms before we engage in a meaningful discussion, I would suggest to start by reading three small chapters from the User Manual:
You forgot the first part of that advice:
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.
So, the thing is, you're using program A that uses program B that uses program C (Docksal uses Docker, which uses VirtualBox). How do you know which one to blame? A, B, or C? You got to break the problem down. Standalone VirtualBox, then Docker using VirtualBox, then Docksal using Docker using VirtualBox.
Second point was if the CPU is used, look at your guest. What's eating the CPU in your guest? I don't even know what the guest is, but if it's Linux try "top".
Third point was to try to run the guest as a standalone VirtualBox VM and observe if the CPU is high or not, a reiteration pretty much of the first point.
Remember that we only support standalone VirtualBox here. Docker is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. It is not supported on these VirtualBox user forums, they have their own
support channels. I don't even know about Docksal.